Connect Connect and your agent gets 7 tools, among them odei_connect_handshake, odei_connect_plan, odei_connect_report_step. It answers at https://api.odei.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Governed personal world model and memory for your AI agent. Pair once, connect over MCP.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
odei_connect_handshake | Verify an app.odei.ai pairing code and open an ODEI Connect session. Inputs: pairing_code, agent |
odei_connect_plan | Return the ordered local ODEI install plan and reporting contract. Inputs: session_token, os |
odei_connect_report_step | Record evidence that a Connect ceremony step has completed. Inputs: session_token, step, evidence, notes, os |
odei_connect_status | Return current ODEI Connect ceremony progress. Inputs: session_token, os |
odei_connect_talk | Answer from ODEI Connect session state without invoking a model API. Inputs: session_token, message, os |
wm_recall | Read facts back from your ODEI-hosted operator memory. Simple substring + recency match (v1) — no semantic search yet. Inputs: query, limit, session_token |
wm_remember | Write one fact to your operator memory in ODEI — the World Model grows from it. Server-side (ODEI-hosted) memory for the paired operator; not the local world-model capsule. Inputs: fact, kind, session_token |
Every block below points at https://api.odei.ai/mcp. Pick your client and copy.
claude mcp add --transport http connect https://api.odei.ai/mcp
{
"mcpServers": {
"connect": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.odei.ai/mcp"]
}
}
}{
"mcpServers": {
"connect": {
"url": "https://api.odei.ai/mcp"
}
}
}{
"servers": {
"connect": {
"type": "http",
"url": "https://api.odei.ai/mcp"
}
}
}{
"context_servers": {
"connect": {
"url": "https://api.odei.ai/mcp"
}
}
}{
"mcpServers": {
"connect": {
"serverUrl": "https://api.odei.ai/mcp"
}
}
}{
"mcpServers": {
"connect": {
"url": "https://api.odei.ai/mcp"
}
}
}name: Connect
version: 0.0.1
schema: v1
mcpServers:
- name: Connect
type: streamable-http
url: https://api.odei.ai/mcp{
"mcpServers": {
"connect": {
"httpUrl": "https://api.odei.ai/mcp"
}
}
}{
"mcpServers": {
"connect": {
"type": "http",
"url": "https://api.odei.ai/mcp"
}
}
}{
"mcpServers": {
"connect": {
"url": "https://api.odei.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.odei.ai%2Fmcp&type=streamable_http&id=connect&name=Connect
It answered our last check on 17 October 2026 in 435 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by odei.ai and served from api.odei.ai, the vendor's own domain: https://api.odei.ai/mcp.
7, as returned by the server's own tools/list on 8 September 2026: odei_connect_handshake, odei_connect_plan, odei_connect_report_step, odei_connect_status, odei_connect_talk, wm_recall, wm_remember.
It answered our last check on 17 October 2026 in 435 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.odei.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.odei. Endpoint host: api.odei.ai. ARD identifier: urn:air:ai.odei:mcp:connect.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.