MCP Access

MCP Access lets you connect external AI clients, Claude Desktop and Cursor, to your Orgn workspace over the Model Context Protocol (MCP). Once connected, these clients can interact with your tasks and projects using the same tools available to the in-app Ask Orgn assistant.

MCP Access is accessible from Settings → MCP Access in the left sidebar.

Personal Access Token

To connect an external client, you first need to generate a personal access token.

Click Generate token to create one. The token is shown once only: copy it immediately and store it securely. It expires automatically after 30 days. There is no per-token revoke; to invalidate a token before it expires, generate a new one, which replaces the previous one.

Once generated, an orange notice confirms the expiry date and reminds you to copy it immediately. A toast notification at the bottom right also confirms the token was created. The Client configuration block updates automatically to include your token in the Authorization header, ready to copy into your client.

Client Configuration

The Client configuration section provides the JSON snippet you need to add to your external AI client. Copy it using the copy button and add it to:

• Claude Desktop: paste into claude_desktop_config.json
• Cursor: paste into ~/.cursor/mcp.json

Restart the client after pasting. The Orgn tools appear automatically once the client connects.

Replace <your-token> in the config with the token you generated, or copy the pre-filled version directly from the page after generating.

What the Token Can Do

The token grants read and write access scoped to your account and the teams you belong to. With it, external clients can:

• Search and create tasks
• Manage cycles, milestones, labels, and comments
• Read and write projects

The token cannot delete tasks or docs, change statuses in bulk, or run long scans. Use the web app for those actions.

Security

Treat the token like a password, anyone who has it can act as you over MCP. Key points to keep in mind:

• Tokens expire automatically after 30 days.
• Tokens are shown only once at generation time and cannot be retrieved afterwards.
• There is no per-token revoke. To invalidate a token before it expires, generate a new one, which replaces the previous token.