Manual MCP Setup
Use this path when your AI tool supports remote MCP with OAuth. The setup is one URL plus a Kwilt sign-in. There are no tokens to paste.
Start with compatibility
Kwilt currently connects through remote MCP. Your AI tool needs support for remote MCP and OAuth before it can complete the sign-in flow.
If the tool supports that path, manual setup gives it access to the same Kwilt tools and scopes the app uses for connected agents.
Add the Kwilt MCP server
In your AI tool, open the MCP server or connector settings and add a new remote MCP server.
Use https://auth.kwilt.app/functions/v1/mcp as the URL. Pick a name like "Kwilt" so you can recognize it later.
- Server URL: https://auth.kwilt.app/functions/v1/mcp
- Connection type: remote MCP / streamable HTTP
- Authentication: OAuth (handled for you)
- Permissions: read/write scopes shown on the Kwilt consent screen
Complete the Kwilt sign-in
The first time your AI tool calls a Kwilt tool, it should open a Kwilt sign-in page on go.kwilt.app. Sign in with the Apple or Google account you use in the Kwilt mobile app, then approve the connection.
Your AI tool stores the resulting access token. Future calls reuse it until it expires or you revoke it.
If your tool asks for a bearer token
If the setup screen asks you to paste a long bearer or personal access token, your tool is not on the supported public path. The current Kwilt remote MCP only accepts OAuth-issued access tokens, not user-pasted PATs.
Either wait for your AI tool to support remote MCP with OAuth, or use a compatible client that already supports that flow.
How to know it worked
Ask the agent for something that needs Kwilt, like "summarize my current Arcs" or "capture a To-do called book the appointment." If the agent calls a Kwilt tool and references your real data, the connection is working.
If it falls back to generic answers, recheck the server entry, that you completed the sign-in, and that your AI tool actually supports remote MCP with OAuth.