Codex MCP Setup
Codex can connect to Kwilt through the Kwilt Remote MCP server when remote MCP with OAuth is available in your environment. This is the MCP setup path, not a separate Kwilt plugin yet.
What you add
Add the Kwilt MCP server URL in Codex's MCP settings. The first tool call should open the Kwilt consent flow so you can sign in and approve the requested scopes.
Authentication happens through a Kwilt sign-in page on go.kwilt.app. You do not paste tokens.
- Server URL: https://auth.kwilt.app/functions/v1/mcp
- Permissions: read and write access to your Kwilt context
- Setup type: remote MCP with OAuth
Connect and enable
Open Codex's MCP settings, add the Kwilt server URL, and enable it. The first time the agent calls a Kwilt tool, Codex opens a Kwilt sign-in page.
Sign in with the Apple or Google account you use in the Kwilt mobile app, then approve the connection. Codex stores the resulting access token.
How to know it worked
Ask Codex something that needs your Kwilt context, like "what is my current show-up streak?" The agent should call a Kwilt tool and report your real number.
If Codex does not have access, recheck that the plugin is enabled and that the sign-in tab finished without errors.
If something goes wrong
If Codex asks for a bearer token instead of opening a Kwilt sign-in page, you are not on the supported public path. Remove that entry and use OAuth-based remote MCP instead.
If your Codex environment does not support remote MCP with OAuth, wait for that support before connecting Kwilt.