mcpbeat

Connect MCP Server

ai.odei/connect
answering

Connect is answering right now. Last checked 7 min ago. It exposes 7 tools.

Governed personal world model and memory for your AI agent. Pair once, connect over MCP.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
465 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add connect --transport http https://api.odei.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "connect": {
      "url": "https://api.odei.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.connect]
url = "https://api.odei.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "connect": {
      "url": "https://api.odei.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "connect": {
      "url": "https://api.odei.ai/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

odei
odei_connect_handshake
Verify an app.odei.ai pairing code and open an ODEI Connect session.
odei_connect_plan
Return the ordered local ODEI install plan and reporting contract.
odei_connect_report_step
Record evidence that a Connect ceremony step has completed.
odei_connect_status
Return current ODEI Connect ceremony progress.
odei_connect_talk
Answer from ODEI Connect session state without invoking a model API.
recall
wm_recall
Read facts back from your ODEI-hosted operator memory. Simple substring + recency match (v1) — no semantic search yet.
remember
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.

Endpoints

URLTransportStateLatencyChecked
https://api.odei.ai/mcp streamable-http answering 439 ms 7 min ago

Connect — questions

Answers built from our own checks of this server.

What can Connect do?
It exposes 7 tools, read directly from the server on our last check. Among them: odei_connect_handshake, odei_connect_plan, odei_connect_report_step, odei_connect_status, odei_connect_talk, wm_recall and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Connect working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 465 ms. The bar chart above shows every period we have measured.
Is Connect still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Connect?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Connect need an API key?
No. Connect completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Connect?
It answers our handshake in 465 ms on average, which is faster than 25% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.