Connect Claude.ai

Claude.ai supports custom MCP connectors via OAuth. Once added, you can ask Claude to read or change your Moly workspace right inside any conversation.

Before you start

You'll need:

• A Moly account on a workspace you can access
• Claude.ai (any tier — custom connectors are available on free and paid plans)

Steps

1. In Claude.ai, click Settings → Connectors.
2. Click Add custom connector at the bottom of the connectors list.
3. Fill in:
   • Name: Moly
   • Remote MCP server URL: https://api.moly.so/mcp
4. Leave OAuth Client ID and OAuth Client Secret blank — Moly's connector self-registers Claude through Dynamic Client Registration.
5. Click Add.

Claude.ai opens a popup with the Moly login screen. Sign in with your normal Moly credentials. Claude.ai redirects back automatically and the new connector appears in your list.

Verify it's working

In a new conversation, ask Claude:

List my Moly workspaces.

Claude should respond with the workspaces you're a member of. If you see an authentication error, troubleshoot below.

What Claude.ai can do

After connecting, Claude can:

• Read tasks across your workspaces (search, filter, fetch by id)
• Create / update / complete / archive tasks
• Manage checklists, comments, labels, links between tasks
• Read and write pages
• See attachments and metadata (but not download file bodies — that's still Moly-only)
• Walk the project / space / workspace hierarchy

It cannot access billing, account settings, or anything outside the MCP scope set.

Revoking access

In Moly:

1. Go to Settings → Integrations → Connected MCP clients.
2. Find the row labelled "claude-ai" (or whatever name Claude.ai self-registered with).
3. Click Disconnect.

Claude.ai loses access immediately. Its next request will get a 401 and the connector will show as disconnected in Claude.ai's UI within ~15 minutes.

In Claude.ai, you can also remove the connector from Settings → Connectors — the underlying Moly session is still cleaned up by Moly's revoke endpoint.

Troubleshooting

"Failed to connect" right after clicking Add

• Confirm the URL is exactly https://api.moly.so/mcp (no trailing slash, no /v1).
• If you're on a self-hosted Moly deployment, use your custom URL.
• Try clearing Claude.ai's connector cache: refresh the page, then re-add.

"No active Moly account is linked to this Cognito identity"

This means you logged into the Cognito popup with an email Moly doesn't have an active user for. Make sure you're using the same email you sign into the Moly web app with.

Claude can list workspaces but can't write

You connected with read-only scopes. Disconnect, then re-add — Claude.ai requests read, write, and admin by default. If your admin has restricted what scopes the connector is allowed to ask for, contact your workspace admin.

Connector keeps disconnecting

The session may be revoked from Moly's side. Check Settings → Integrations → Connected MCP clients — if the row is missing, someone revoked it; if it's there, restart the Claude.ai app.