Work Context Protocol MCP Server

by workcontextprotocol Your server? Claim it

answering

Work Context Protocol is answering right now. Last checked 8 min ago.

Persistent work tracking for AI agents: tasks, status and history that follow you across machines

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

184 of 184 checks

—

Tools

hidden behind auth

451 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Work Context Protocol 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 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wcp --transport http https://workcontextprotocol.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "wcp": {
      "url": "https://workcontextprotocol.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.wcp]
url = "https://workcontextprotocol.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wcp": {
      "url": "https://workcontextprotocol.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "wcp": {
      "url": "https://workcontextprotocol.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://workcontextprotocol.io/mcp	streamable-http	needs key	539 ms	8 min ago
https://workcontextprotocol.io/mcp?src=registry	streamable-http	needs key	516 ms	8 min ago

Alternatives to Work Context Protocol

same job, measured the same way

Agentram MCP

by seanmarkwei

Model Context Protocol server for AgentRAM. Persistent memory for AI agents.

18 installs/wk local only

todo.vu

by mooball

Model Context Protocol server for todo.vu task management and time tracking.

answering

Memoir

by camgitt

Persistent memory for AI coding tools via MCP. Remembers across sessions and machines.

183 installs/wk local only

MCP Context Server

by alex-feel

An MCP server that provides persistent multimodal context storage for LLM agents.

472 installs/wk local only

MCP Memento

by annibale-x

An MCP server that provides persistent memory and context management across sessions

197 installs/wk local only

Openfuse MCP

by openfused

Encrypted mail, shared memory, and persistent context for AI agents.

28 installs/wk local only

Goldhold

by jerrysrodz

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

54 installs/wk answering

memex

by kioie

Local MCP memory for coding agents. SQLite on your machine — preferences persist across chats.

local only

Work Context Protocol — questions

Answers built from our own checks of this server.

Why is there no tool list for Work Context Protocol?

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

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

How do I connect Work Context Protocol?

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. 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 Work Context Protocol?

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

It answers our handshake in 451 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.