Connect your AI to ODEI

Streamable HTTP, stateless. One JSON-RPC request per HTTP call. Methods: initialize, tools/list, tools/call. There is no MCP session and JSON batches are refused. A token is bound to one resource: a /mcp token does not work on /mcp/coding.

Listing a tool grants nothing. Dispatch checks every call.

The first message everywhere is: Show my ODEI wallet. Visiting a setup page creates no connection and grants nothing. The public guide with one-click links and copyable commands is my.odei.ai/connect. Short links: /connect/claude, /connect/claude-admin, /connect/chatgpt, /connect/grok, /connect/cursor, /connect/vscode, /connect/codex, /connect/claude-code.

Claude

1. Open my.odei.ai/connect/claude, or on the Claude website open Customize, Connectors, Add custom connector.
2. Name it ODEI, use server URL https://my.odei.ai/mcp, connect, sign in to ODEI and allow access.
3. The mobile app cannot add connectors. Add ODEI in any browser, then in a chat use + then Connectors and switch ODEI on.

Connected when Customize, Connectors lists ODEI as connected. The Free plan allows one custom connector. On Team and Enterprise an Owner adds it (/connect/claude-admin) and members select Connect. Connectors added on claude.ai also load in Claude Code on the same account.

If Claude could not reach the server, check the URL exactly. On Free, remove the other connector.

ChatGPT

1. On chatgpt.com in a desktop browser open Plugins, +, Add custom MCP server. my.odei.ai/connect/chatgpt redirects there.
2. Name it ODEI, use https://my.odei.ai/mcp, choose OAuth, leave Client ID and Client Secret empty, tick the acknowledgement, select Create as a plugin.
3. Select Sign in with ODEI, then Allow access. Install from personal Plugins, start a new chat, type @ and pick ODEI.

Connected when ODEI shows Installed in Plugins and @ODEI answers in a new chat. Not on the Free plan. Plus and Pro work; some write actions may be limited. Business, Enterprise and Edu: an admin must allow Developer mode. Setup cannot be done from a phone or the ChatGPT apps.

No Add custom MCP server? Turn on Developer mode in Settings, Security and login.

Grok

1. On grok.com/connectors in any browser open New Connector, Custom.
2. Name it ODEI, Server URL https://my.odei.ai/mcp, complete OAuth, Allow access.
3. Start a new Grok chat and ask Grok to use ODEI.

Connected when grok.com/connectors shows ODEI as connected. Adding a custom connector in the Grok mobile app is not documented; add it on the website and use the same account in the app.

To refresh or fix, use Reauthenticate on the existing connector. Removing and re-adding registers a second client and a duplicate authorization.

Gemini app

On gemini.google.com open Settings, Connected apps, Custom apps, if the account has it. Enter https://my.odei.ai/mcp, complete ODEI sign-in and approval, and use the same Google account in the mobile app. Eligible personal accounts only: age 18+, United States, English, Keep Activity enabled.

No Custom apps? This account is not eligible. Use Gemini CLI, Antigravity or another AI.

Claude Code

Run these in your own terminal, not inside a Claude Code chat:

claude mcp add --transport http --scope local odei-remote-claude https://my.odei.ai/mcp/coding
claude mcp login odei-remote-claude

This adds ODEI to the current project folder. For every project use --scope user. An agent can run the add part; sign-in needs an interactive terminal, so the owner runs login. Connected when /mcp lists odei-remote-claude as connected. Claude Code stops waiting 5 minutes after sign-in starts. If the browser says refused to connect, run the login again in the same folder and approve the new tab.

Codex

codex mcp add odei-remote-codex --url https://my.odei.ai/mcp/coding

Codex opens ODEI sign-in in the browser and finishes on its own. If no browser opened, run codex mcp login odei-remote-codex. Over SSH, run it with --no-browser, open the link on any computer, approve, and paste the link from the ODEI Connected page back. Remove with codex mcp remove odei-remote-codex. Connected when /mcp in Codex lists odei-remote-codex with its tools.

Cursor

Use the Add to Cursor button on my.odei.ai/connect, or Settings, Tools & MCP, Add Custom MCP, or the file ~/.cursor/mcp.json (.cursor/mcp.json for one project):

{"mcpServers":{"odei-remote-cursor":{"url":"https://my.odei.ai/mcp/coding"}}}

Choose Connect next to odei-remote-cursor and approve in the browser. Connected when Settings, Tools & MCP shows it with a green dot and its tools. Cursor receives sign-in on port 8787. If sign-in did not finish, quit any app on that port and choose Connect again.

VS Code

Use the Add to VS Code button on my.odei.ai/connect, or:

code --add-mcp '{"name":"odei-remote-vscode","type":"http","url":"https://my.odei.ai/mcp/coding"}'

Or run MCP: Add Server with HTTP, or commit a root .mcp.json for one repository (.vscode/mcp.json is deprecated). Allow odei-remote-vscode to sign in when asked. Needs GitHub Copilot; the Free tier counts. On Copilot Business or Enterprise the MCP servers in Copilot policy must be on. Connected when MCP: List Servers shows it running. No ODEI tools in Copilot Chat? Switch to Agent mode and turn on odei-remote-vscode in the tools menu.

Gemini CLI

gemini mcp add --transport http --scope user odei https://my.odei.ai/mcp/coding

Start gemini, run /mcp auth odei, approve in the browser, check with /mcp. Needs Gemini Code Assist Standard or Enterprise, or your own paid Gemini API key from Google; ODEI itself needs no key. Consumer access ended on 2026-06-18. Needs a local browser, so not over SSH or in containers. Remove with gemini mcp remove --scope user odei.

Antigravity CLI

agy mcp add odei https://my.odei.ai/mcp/coding

Then Agent settings, Customizations, Authenticate next to odei, sign in, copy the code shown, paste, Submit. Connected when agy mcp list shows odei as enabled. Listed but disabled: run agy mcp enable odei, then Authenticate again. Remove with agy mcp remove odei.

Devin Desktop (formerly Windsurf)

Open Cascade, MCP menu, Open MCP config file. Add this to ~/.config/devin/mcp_config.json (Windows %APPDATA%\devin\mcp_config.json; older Windsurf ~/.codeium/windsurf/mcp_config.json), save, refresh, sign in when asked:

{"mcpServers":{"odei-remote-windsurf":{"serverUrl":"https://my.odei.ai/mcp/coding"}}}

Do not use windsurf --add-mcp; it writes a setting Cascade ignores. On a Teams plan an admin allowlist blocks servers not on it.

Grok Build

grok mcp add --transport http --scope user odei-remote-grok https://my.odei.ai/mcp/coding

Run grok, type /mcps, select odei-remote-grok and press i to sign in. Grok Build has no mcp login command. Tools missing? Open /mcps, select it and reconnect, or restart.

Any other MCP client

Chat apps use https://my.odei.ai/mcp. Coding agents and IDEs use https://my.odei.ai/mcp/coding as a streamable HTTP server. OAuth with dynamic client registration: leave client ID and secret empty. Connected when the client lists ODEI tools such as odei_overview.

The owner picks one level per area on the consent page. An account with a verified identity can connect an AI.

odei_wallet_propose needs Read and prepare operations. Read and save proposals is not enough.

Defaults for a new connection

These defaults apply when the client requests the default access.

• The coding defaults also apply when ODEI identifies the client as a coding agent, even on /mcp.
• Every write outside Wallet is opt-in under Customize access. Publishing on Network is off by default.
• An explicit narrow request preselects what it asked for, minus writes outside Wallet.
• Reconnecting an existing connection with the generic request preselects its current access, not these defaults.
• An existing connection needs a new consent to widen access. Refreshing a tool list never adds access.

Scopes

A dependency missing from the set makes the request invalid_scope. A tool's required scopes appear on its descriptor in securitySchemes[0].scopes and _meta.securitySchemes. capital.manage exists in the vocabulary but is never advertised or offered to external clients. Existing grants may keep it, and it gates no execution.

Owner limits

Separately from each grant, the owner can deny scopes for all connections, in My ODEI. A connection's effective access is its grant minus those denials. Denying a read also blocks its write. odei_overview shows it in areas[].ownerLimited (summary) and ownerPermission (full), and odei_agent_profile connections_get reports effective scopes.

These scopes can be denied: network.read, network.write, research.read, research.write, work.read, work.write, messages.read, messages.write, economy.read, capital.propose, capital.plan, agent.manage.

• A grant lasts 30 days and is not extended by token refresh.
• Re-consent is the only renewal. It creates a new grant, which also lists the current tools.
• Within 3 days of expiry, notices carry reconnectBy, and Connectors shows Access ends with a Review access button.
• After expiry the agent gets 401 with This connection is outdated or revoked. Reconnect at https://my.odei.ai/connect.
• Connections are per ODEI account. An AI approved while signed in to another account sees no wallet.
• An account can hold 10 active connections and 100 connections in its lifetime. At 10, the consent page asks the owner to choose one app connection to end. Nothing ends if they cancel.

The owner manages connections in My ODEI, Agent, Connectors. Agents cannot read this page. Each row shows the AI, its status such as Connected with when it was last used, its access in the same words as the consent page, raw permissions under Details, Last used and Expires. Connected means authorization state. It is not a heartbeat or proof that a tool worked.

Activity

Open Activity on a row to see what this AI changed or tried to change.

• One row per call to a tool that can change something, through /mcp or /mcp/coding. Reads are not listed. A preview cancel is not listed.
• A row holds fixed labels: the tool, the action, the outcome (done, needs approval, refused, failed) and the id of the object changed. It never holds arguments, titles, bodies, amounts, addresses or message text.
• Rows are kept 30 days, up to 300 per connection. The page shows the newest 50.
• Empty state: Nothing changed through this connection in the last 30 days.

Revoke access

On a Connectors row choose Revoke access, then Revoke now. Access ends at once, the row shows Access revoked, and the agent gets 401 with the reconnect message. Agents have no disconnect tool. Revoking a connection cancels no signed transaction and no Auto setting; those are managed in Wallet.

ODEI records the catalog version each connection last listed. If it differs, or the client called a hidden legacy name after listing, the connection is marked outdated. Agents see catalog.check in every odei_overview and a connectorUpdate notice when there is evidence. Refreshing the list changes no grant and never adds access. A notice never changes the result.

For authors of MCP clients. Normal clients do all of this for you. Only response type code, grants authorization_code and refresh_token, token endpoint auth method none, PKCE S256, bearer in the header only. Authorization responses carry iss.

Redirect URIs: https; http only on localhost, 127.0.0.1 or [::1] (any port matches a registered loopback URI); private schemes cursor, vscode, vscode-insiders, windsurf, antigravity. No userinfo, fragment, or code, state or error query keys. Client name and logo are unverified.

Issued tokens always carry exactly the owner-approved grant, whatever scope the client resends. A refresh never widens access. Refresh tokens are single use with a 15 second grace for a lost response. Replaying an exchanged code, or reusing a refresh token outside the grace window, revokes the whole grant.

Errors are on the errors page. Rate limits are on the limits page.