Context Engine MCP Server

by relote-com Your server? Claim it

answering

Context Engine is answering right now. Last checked 7 min ago.

One memory for your AI agents and your team: Claude, ChatGPT, Cursor and your agents share it.

Uptime history 21 hours of history

21 hours agonow

100.0%

Uptime 24h

75 of 75 checks

—

Tools

hidden behind auth

150 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Context Engine every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add context-engine --transport http https://app.contextengine.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://app.contextengine.com/mcp

~/.codex/config.toml

[mcp_servers.context-engine]
url = "https://app.contextengine.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "context-engine": {
      "url": "https://app.contextengine.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "context-engine": {
      "type": "http",
      "url": "https://app.contextengine.com/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

URL	Transport	State	Latency	Checked
https://app.contextengine.com/mcp	streamable-http	sign-in	148 ms	7 min ago

Alternatives to Context Engine

same job, measured the same way

knowsme

by knowsme

One memory for you and your AI agents, shared by ChatGPT, Claude, Gemini, Grok, Codex and Cursor.

answering

MemoryComb

by bryceblackroot

One memory for every AI: Claude, ChatGPT and more share a memory that lives on your computer.

local only

Memory Bridge

by memorybridgeai

One memory for all your AI tools: Claude, ChatGPT, Cursor and any MCP client share the same notes.

answering

Vibsync

by vibsync

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

answering

Brain Memory

by brainmemory

Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.

answering

LinkGents

by linkgents

Connect Claude, ChatGPT, Muse, Claude Code and Codex to one shared context and one team board.

answering

Modelbrain

by modelbrain

One memory for Claude, ChatGPT and Cursor, kept on your computer. Optional sync, encrypted first.

42 installs/wk answering

Contexel

by contexel

Shared AI memory. ChatGPT, Claude, Cursor and any MCP app read and write the same memory.

answering

Context Engine — questions

Answers built from our own checks of this server.

Why is there no tool list for Context Engine?

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 Context Engine working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 75 of 75 checks got a reply (100.0%), average response time 150 ms. The bar chart above shows every period we have measured.

How do I connect Context Engine?

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 Context Engine?

No API key is involved. Context Engine 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 Context Engine?

It answers our handshake in 150 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.