AI assistant integration (MCP)
Connect ChatGPT, Claude, Cursor, Grok Bot, GitHub Copilot, or any MCP client to your projects with a single URL.
Connect an assistant so it can read your projects and update actions for you. You only give it this server URL. The first time it connects, you sign in to Action Log in the browser.
Server URL
https://www.actionlog.app/mcp
This is the address for the Action Log site you are using now.
Claude.ai on the web
This is the path most people use. In Claude, open Settings → Connectors → Add custom connector. Name it Action Log, paste the server URL above, and save. Claude asks you to sign in the first time you use it.
Claude Desktop
Open Settings → Connectors and add a custom connector with the same URL. If your version has no Connectors screen, add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop:
{
"mcpServers": {
"actionlog": {
"url": "https://www.actionlog.app/mcp"
}
}
}How authentication works
On first connection, your AI client opens a browser window to the Action Log login page. Log in as normal and you are redirected back automatically. The client refreshes that sign-in on its own, so you stay connected while you keep using it. Open Connected assistants in your account menu to disconnect one. No tokens are stored in your client configuration file.
Claude Code
Run this once in your terminal:
claude mcp add --transport http actionlog https://www.actionlog.app/mcp
Claude Code will prompt you to log in on first use. After that, ask Claude anything about your projects and actions.
VS Code (GitHub Copilot)
Open VS Code Settings and search for MCP, then click Edit in settings.json and add:
{
"mcp": {
"servers": {
"actionlog": {
"url": "https://www.actionlog.app/mcp"
}
}
}
}Reload VS Code. Copilot will prompt you to authenticate on first use.
Cursor
Open Cursor Settings → Tools & Integrations → MCP, click Add new MCP server, set the name to actionlog and the URL to https://www.actionlog.app/mcp, then save and reload.
ChatGPT
In a ChatGPT workspace that allows custom MCP servers, choose Add custom MCP server. Set the name to Action Log, the server URL to https://www.actionlog.app/mcp, and authentication to OAuth. Leave the advanced OAuth settings as discovered, confirm the custom server notice, and save.
ChatGPT opens the Action Log sign-in page the first time it connects.
Grok Bot
Add a remote MCP server with the URL https://www.actionlog.app/mcp. Grok Bot opens the Action Log sign-in page on first use.
Other MCP clients
Any client that supports remote MCP servers with OAuth can connect using the same URL. Action Log supports both dynamic client registration and client ID metadata documents, so there is nothing to register by hand.
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 allow the operation. Viewers cannot create or update actions.
- Connected but no projects appear — confirm you are logged in to the correct Action Log account.
- redirect_uri is not allowed — usually means your MCP client uses a callback URL the server does not recognize. Cursor desktop uses cursor://anysphere.cursor-mcp/…; Cursor cloud agents (including Grok) use https://www.cursor.com/agents/mcp/oauth/callback. Cloud deployments are updated with supported prefixes; on self-hosted instances, add the client's prefix to Mcp__AllowedRedirectUriPrefixes.