OpenAI, Codex, and Claude MCP
Dainvo's remote MCP connection lets OpenAI, Codex, or Claude work with the Dainvo data you select in the desktop app. It does not replace the model used inside Dainvo and it does not turn your desktop database into a public cloud database.
The connection is off by default. It is available to paid personal accounts. Managed enterprise accounts also need an organization administrator to allow the corresponding OpenAI or Claude MCP policy.
Before you connect
- Update to a Dainvo desktop release that supports external MCP connections.
- Sign in to Dainvo with the account you want OpenAI or Claude to use.
- Keep the Dainvo desktop open while using the connection.
- Open Settings > AI and select at least one data category the provider may access.
The provider sees only the tool inputs and results needed for the requests you make, within the data categories selected in Dainvo.
OpenAI
The OpenAI card covers both ChatGPT and Codex in the unified OpenAI app.
- Open Settings > AI > OpenAI in Dainvo.
- Select the Dainvo data categories you want to make available.
- Choose Connect. Dainvo activates the encrypted desktop relay and opens this setup guide.
- In the OpenAI app, open Manage plugins, skills, and MCPs and install the Dainvo plugin if it is listed.
- Choose Authenticate for Dainvo. Your browser opens
users.dainvo.com; sign in to the same Dainvo account, review the identity scopes and desktop/data readiness, and choose Allow. - Return to the OpenAI app. Dainvo changes from Awaiting authorization to Connected after the OAuth grant exists and this desktop is online.
You do not need Developer Mode, an OpenAI API key, a bearer token, or a Dainvo URL containing your account ID.
OpenAI manual setup
Until the public Dainvo plugin listing is approved, use the custom MCP option in Manage plugins, skills, and MCPs:
| Field | Value |
|---|---|
| Type | Streamable HTTP |
| Name | Dainvo |
| URL | https://mcp.dainvo.com/mcp |
| Bearer token | Leave blank |
| Headers | Leave blank |
Save the MCP and then choose Authenticate. Do not use the STDIO option and
do not enter openai-dev-mcp, a Supabase URL, or a locally generated token.
Claude
Custom remote connectors are intended for ordinary Claude users as well as managed organizations; an enterprise Dainvo account is not required.
- Open Settings > AI > Claude in Dainvo.
- Select at least one Dainvo data category and choose Connect.
- In Claude, open Settings > Connectors and add the Dainvo connector from the directory if it is listed.
- Until the directory listing is approved, add a custom remote connector with
the URL
https://mcp.dainvo.com/mcp. Leave bearer-token and header fields blank. - Choose Connect or Authenticate. In the browser, sign in at
users.dainvo.com, review the request, and choose Allow. - Return to Claude and wait for Dainvo to show Connected.
How the URL knows your account
https://mcp.dainvo.com/mcp is the same public service address for everyone.
It does not identify an account by itself. When you authenticate, Dainvo signs
you in through OAuth and issues a grant tied to your Dainvo account and the
recognized OpenAI/Codex or Claude client. Every MCP request must present that
grant. Dainvo then routes the encrypted request only to the active desktop
signed in to that account.
Never put an account ID, password, access token, or bearer token in the URL.
Connection states
- Off: the provider cannot call Dainvo tools.
- Plan required: the signed-in personal account does not have paid access.
- Blocked by organization: a managed account policy does not explicitly allow this provider.
- Data access required: no Dainvo data category has been selected.
- Awaiting authorization: the desktop route is active, but a recognized OAuth grant has not been completed.
- Connected: a recognized grant exists and this desktop route is live.
- Active on another device: another signed-in Dainvo desktop owns the route.
- Desktop offline: authorization exists, but the active desktop is not responding.
Disconnect
Open Settings > AI, choose the OpenAI or Claude card, and select Disconnect. Dainvo disables the desktop route and revokes every recognized grant for that provider. Removing the MCP or connector in the provider does not by itself enable the Dainvo connection again.
Troubleshooting
- Authenticate does nothing: confirm you saved a Streamable HTTP MCP with the exact production URL and no bearer token or headers. Remove older Dainvo entries that use a Supabase URL, then add the current endpoint again.
- No browser opens: allow the OpenAI or Claude app to open your default browser, then retry Authenticate.
- Dainvo remains Awaiting authorization: finish the browser Allow step with the same Dainvo account and keep the desktop open.
- Desktop offline: reopen Dainvo, sign in, and leave it running.
- Data access required: select at least one category under Settings > AI.
- Blocked by organization: ask the Dainvo organization administrator to allow OpenAI MCP (ChatGPT and Codex) or Claude MCP.
Data handling
Primary Dainvo calendar, task, bucket, rule, and settings data remains on the desktop. Dainvo stores encrypted request and result envelopes transiently in Supabase so the remote provider can reach the selected desktop. Cloudflare and Supabase process the connection without content logging. The OpenAI or Claude service receives the tool inputs and results required to answer the request and handles them under that provider's terms and privacy policy.