Cursor MCP Setup
Cursor can connect to Kwilt through the Kwilt Remote MCP server when your Cursor version supports remote MCP with OAuth. This is not a separate Kwilt plugin yet; it is the standards-based MCP path.
What you add
Add the Kwilt MCP server URL in Cursor's MCP or tools settings. Cursor should use OAuth to complete the Kwilt sign-in instead of asking you to paste a bearer token.
You do not paste any tokens. Cursor handles the OAuth handshake with Kwilt for you.
- Server URL: https://auth.kwilt.app/functions/v1/mcp
- Permissions: read and write access to Arcs, Goals, To-dos, Chapter notes, and show-up context
- Setup type: remote MCP with OAuth
Connect and enable
Open Cursor's Tools and MCP settings, add the Kwilt server URL, and enable it. Cursor will open a Kwilt sign-in page on go.kwilt.app the first time the agent tries to use a Kwilt tool.
Sign in with the same Apple or Google account you use in the Kwilt mobile app. Approve the connection. Cursor stores the resulting access token for you.
How to know it worked
Ask your Cursor agent to do something concrete, like "create a Goal in Kwilt for finishing the launch checklist" or "what Arcs am I working on right now?" The agent should call a Kwilt tool and reflect your real Kwilt data.
If the agent claims it does not have access to Kwilt, recheck the plugin is enabled and that the sign-in tab finished without errors.
If something goes wrong
If Cursor opens a token field instead of a Kwilt sign-in page, that path is not supported by Kwilt yet. Remove the entry and use the OAuth-based remote MCP setup instead.
If your Cursor version does not support remote MCP with OAuth, wait for that support before connecting Kwilt.