mcpbeat Sign in

Throughline MCP Server

by getthroughline Your server? Claim it
answering

Throughline is answering right now. Last checked 13 min ago.

A persistent AI self you own — memory, persona, judgment — portable across all your AI hosts.

Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
372 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Throughline missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add throughline --transport http https://getthroughline.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://getthroughline.ai/mcp
~/.codex/config.toml
[mcp_servers.throughline]
url = "https://getthroughline.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "throughline": {
      "url": "https://getthroughline.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "throughline": {
      "type": "http",
      "url": "https://getthroughline.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://getthroughline.ai/mcp streamable-http sign-in 338 ms 13 min ago

Alternatives to Throughline

same job, measured the same way
Justonce Memory
by bluesoul-technology

Persistent, portable, bitemporal memory layer — recalled proactively across your AI tools.

answering
Strata
by agenerationforwordz-tech

Self-hosted AI memory server. Persistent memory on your hardware, not the cloud.

29 installs/wk local only
Memoro
by circassian1977-byte

Personal AI memory layer on your own computer. Read/write durable memory across MCP clients.

21 installs/wk local only
Memento
by mementoagi

Hosted MCP memory for coding agents: persistent across sessions, editable markdown, team sharing.

answering
Memory Vault
by apurv101

Portable AI memory shared across models and harnesses - plain markdown you own.

86 installs/wk answering
MCP Memory
by infoinlet-marketplace

Persistent searchable memory for AI agents — save/get/search across sessions, tags.

52 installs/wk local only
Goldhold
by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

93 installs/wk answering
Memoir
by bighippoman

Structured session journals for AI agents. Persistent memory across sessions.

37 installs/wk local only

Throughline — questions

Answers built from our own checks of this server.

Why is there no tool list for Throughline?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Throughline 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 372 ms. The bar chart above shows every period we have measured.
How do I connect Throughline?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Throughline?
No API key is involved. Throughline answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Throughline?
It answers our handshake in 372 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.