Connect Cursor
Add Moly as an MCP server in Cursor to let the AI agent read and modify your tasks.
Connect Cursor
Cursor supports remote MCP servers via OAuth. Once added, the AI agent can list tasks, file work items, and update pages while you code.
Before you start
You'll need:
- Cursor 0.45 or newer (MCP remote-server support landed in late 2025)
- A Moly account
Steps
- Open Cursor → Settings → Cursor Settings → MCP.
- Click Add new MCP server.
- Choose Remote (OAuth) as the transport.
- Set:
- Name: moly
- URL:
https://api.moly.so/mcp
- Save. Cursor opens a browser tab with the Moly login flow.
- Sign in to Moly. Cursor's browser hands the credential back automatically.
Cursor's MCP panel should now show moly as Connected with a list of available tools.
Per-project vs global
By default, Cursor adds the server globally — every project can call it. To restrict it to one project, edit .cursor/mcp.json in your project root:
{
"mcpServers": {
"moly": {
"url": "https://api.moly.so/mcp",
"transport": "http"
}
}
}Cursor handles OAuth credential storage in its own keychain — you don't put tokens in the JSON.
Verify
In Cursor's chat, ask:
What's in my Moly inbox?
The agent should call list_tasks against the Inbox view and return your unscheduled tasks.
Revoking access
In Moly: Settings → Integrations → Connected MCP clients → Disconnect the Cursor row.
In Cursor: Cursor Settings → MCP → Remove the moly server.
Removing it from either side is enough. Both ends will reach consistent state within ~15 minutes.
Troubleshooting
"OAuth handshake failed"
Cursor's MCP OAuth flow needs a working browser and the ability to reach api.moly.so. If you're behind a corporate proxy, allow-list the Cognito Hosted UI domain (it'll be shown in the OAuth popup URL).
Cursor doesn't enumerate tools
Cursor only lists tools after the OAuth flow completes. If the tool list is empty:
- Disconnect in Moly's UI
- Re-add the server in Cursor (it'll prompt for OAuth again)
Multiple Cursor installs sharing one Moly account
Each Cursor install registers as its own MCP OAuth client and appears as a separate row in Settings → Integrations → Connected MCP clients — useful for revoking one workstation without affecting another.