Connect Kwilt to AI Tools
Kwilt can show up inside compatible AI tools through remote MCP. The setup path is intentionally plain: add the Kwilt server URL, sign in on go.kwilt.app, and approve the scopes you want that tool to use.
One server, clear consent
Compatible AI tools connect to the same Kwilt Remote MCP server. The tool may describe that setup as MCP, connectors, custom tools, or servers, but the Kwilt side is the same URL and the same consent screen.
The connection completes through a Kwilt sign-in on go.kwilt.app. No personal access tokens, no copy-pasted bearer strings.
- Server URL: https://auth.kwilt.app/functions/v1/mcp
- Authentication: OAuth through Kwilt sign-in
- Compatibility: any AI client that supports remote MCP with OAuth
What connected tools can do
Connected tools can read compact Kwilt context and, when you approve write access, create, edit, or delete Arcs, Goals, and Activities the same way you would in the app.
Objects created by an agent do not carry special badges in Kwilt. They behave like your own work. Kwilt keeps the connection and action history in Settings so you can review or revoke access.
- Read: Arcs, Goals, recent Activities, latest ready Chapter, and show-up status
- Write: create and update Arcs, Goals, and To-dos
- Delete: use the same recoverable delete behavior as the Kwilt app
- Audit: review connected surfaces and recent write history in Settings → Connected tools
How sign-in works
When you start the connection, your AI tool redirects you to a Kwilt consent page on go.kwilt.app. You sign in with Apple or Google using the same account you use in the Kwilt app, then approve the requested scopes.
Kwilt only ever issues short-lived access tokens to the connected tool. You can revoke a connected tool from Settings → Connected tools in the Kwilt app.
If your tool asks for a bearer token
The current public path uses OAuth, not personal access tokens. If a setup screen asks you to paste a long bearer string, your tool is not on the recommended path yet. Either pick the plugin if one exists for your tool, or wait for OAuth-based remote MCP support.