Blog / Product

Action Log Now Works With Claude, Copilot, Cursor, and Any MCP-Compatible AI

Connect Claude Desktop, VS Code Copilot, Cursor, or any MCP-compatible AI to Action Log with a single URL. Your AI can read projects, manage actions, and post updates — authenticated via your existing login.

By Glen Conway, Founder · · 6 min read

Your project data should not live in a walled garden. Starting today, Action Log exposes a fully authenticated Model Context Protocol (MCP) server — the standard that lets AI assistants call tools on your behalf. Connect once and your AI can read your projects, search actions, post updates, and more, without you copying a single line of data into a chat window.

What this actually means

You are in a standup and your manager asks what is stuck across all active projects. Instead of switching tabs, you ask Claude: "What actions are stuck right now?" It calls Action Log, returns the list, and you answer in ten seconds.

Or you are in Cursor mid-sprint and realise you never logged the decision you just made. You type "Create an action in the Platform project: migrate auth tokens to Redis, assign to me, due in two weeks" and it is done.

No copy-paste. No tab-switching. No manual data entry.

Available tools

Once connected, your AI assistant has access to nineteen tools scoped to your account and your project roles:

ToolWhat it does
create_projectCreate a new project (subject to subscription limits)
update_projectEdit name, description, dates, or meeting cadence
archive_projectArchive a completed project
delete_projectSoft-delete a project (permanent removal after 30 days; owner only)
restore_projectRestore an archived or deleted project to active
list_projectsAll projects you have access to
get_project_detailsFull project with its actions list
get_action_summaryOpen / working / stuck / done counts
get_action_detailsFull action with updates history
search_actionsFilter by status, assignee, keyword, or tag
create_actionCreate a new action in a project
update_action_statusChange an action's status
update_action_assigneesAdd, remove, or replace assignees
update_action_dependenciesSet prerequisite actions (depends-on links)
post_updatePost a progress update on an action
get_project_peopleList project members and roles
list_notificationsYour recent notifications
list_project_integrationsEnabled integrations for a project
link_action_integrationLink an action to DevOps, Basecamp, or Jira by name and ID

Your existing role on each project applies. If you are a Viewer on a project, the AI can read it but cannot write to it — the same rules you would hit in the web app. Creating, editing, archiving, and restoring projects requires Owner or Editor; deleting a project requires Owner.

How authentication works

There is nothing to configure beyond the server URL. Action Log uses OAuth 2.0 Authorization Code + PKCE — the same flow your bank uses, and the one the MCP specification endorses.

When your AI client connects for the first time, it opens a browser window to the Action Log login page. You log in as you normally would. The client receives a short-lived token automatically and stores nothing sensitive in your config file. Tokens last 24 hours; your client re-authenticates when they expire.

Setup: Claude CLI

If you use Claude Code in the terminal, one command is all it takes:

claude mcp add --transport http actionlog https://www.actionlog.app/mcp

Claude will open a browser window for login on first use. After that, ask it anything about your projects and actions directly from your terminal or editor.

Setup: Claude Desktop

  1. Open the Claude Desktop configuration file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json
  2. Add Action Log under mcpServers:

{
  "mcpServers": {
    "actionlog": {
      "url": "https://www.actionlog.app/mcp"
    }
  }
}
  1. Save the file and restart Claude Desktop. On first use, a browser window opens for login — after that it is automatic.

Setup: VS Code (GitHub Copilot)

  1. Open VS Code Settings (Cmd+, / Ctrl+,) and search for MCP.

  2. Click Edit in settings.json and add:

{
  "mcp": {
    "servers": {
      "actionlog": {
        "url": "https://www.actionlog.app/mcp"
      }
    }
  }
}
  1. Reload VS Code. Copilot will prompt you to authenticate on first use.

Setup: Cursor

  1. Open Cursor Settings → Tools & Integrations → MCP.

  2. Click Add new MCP server and enter:

    • Name: actionlog
    • URL: https://www.actionlog.app/mcp
  3. Save and reload. Cursor handles the login flow automatically.

Setup: Any other MCP client

Any client that follows the MCP specification with OAuth 2.0 Authorization Code + PKCE support will work. Point it at https://www.actionlog.app/mcp — auth endpoints are discovered automatically.

Example conversations

Ask for a status snapshot:

"What is the current status breakdown across all my projects?"

Find what needs attention:

"Which actions in the Platform project are stuck or overdue?"

Log a decision fast:

"Create an action in the Infrastructure project: rotate production signing keys, assign to Sarah, due Friday."

Start a new project:

"Create a project called Q3 Platform Integration with a weekly status meeting on Tuesdays."

Wrap up finished work:

"Archive the Acme rollout project — we're done."

Bring a project back:

"Restore the Platform sandbox project — we need it active again."

Stay in flow while coding:

"Post an update on Action 12 in the API project: finished the migration, all tests passing."

Check your inbox:

"Do I have any unread notifications?"

A note on security

Access tokens expire after 24 hours and are never stored in your configuration file. Each login produces a unique token; changing your Action Log password invalidates all active tokens immediately. The MCP server enforces the same role-based access controls as the web application — there is no elevated access path through the AI.

Troubleshooting

"Authentication failed" or redirect loop — your token expired. Disconnect and reconnect the MCP server in your client to trigger a fresh login.

Tool calls return permission errors — your role on that project may not permit the operation. Viewers cannot create or update actions.

Connected but no projects appear — confirm you are logged in to the correct Action Log account.