Work Context Protocol
An open protocol for work continuity, so an AI agent starts the day knowing what happened yesterday.
Open source Open source, with a hosted service at workcontextprotocol.io. Connecting is one command.
Every new agent session starts from nothing. It does not know what you were doing yesterday, what is half-finished, what is blocked, or which decisions were settled and should not be reopened. So you either re-explain the project every morning or you maintain status files by hand.
What it does
WCP gives agents and humans one shared place to track work: items with a status, comments, attached documents, and a history of what happened. An agent picks up an item, reads the description, sees what the last session did, does the work, updates the state, and leaves context for whoever comes next. Nobody maintains it. It gets written while the work is being done.
In Claude Code, connecting takes one line:
claude mcp add --transport http --scope user wcp https://workcontextprotocol.io/mcp
Other clients want the same endpoint in a different box. Cursor takes it in ~/.cursor/mcp.json, Claude on the web takes it as a custom connector, Codex CLI takes it as codex mcp add, and any other MCP client takes it as an HTTP server with a bearer token.
What people use it for
The first thing most people notice is not the tracking. It is that the question “what should I work on today” starts having an answer that the agent can produce without being briefed. One user put it as doing the work and having the work be tracked for him, which is the version of this that matters: the record stops being a thing you maintain and becomes a thing you consult.
Who it is for
For anyone whose real work happens inside an agent across many sessions: Claude Code, Claude in the browser, Cursor, Codex CLI, Lovable, or any client that speaks MCP. It is a work tracker built for agents to write to, so it suits people who want the record kept as a side effect rather than a team that wants a project management tool with a nice board.
The details
| Price | The protocol is open source. The hosted service starts free. |
|---|---|
| How it connects | One MCP endpoint, https://workcontextprotocol.io/mcp, plus a bearer token. |
| Clients | Claude Code, Claude on the web, Cursor, Codex CLI, Lovable, and anything else that speaks MCP. |
| What it stores | Work items with status, comments, attached documents and history, grouped into namespaces. |
| Source | github.com/dpaola2/work-context-protocol |
Questions
How do I install it?
In Claude Code it is one command. In Cursor, Claude on the web and Lovable it is a URL pasted into the MCP or connector settings. The setup page walks through each client.
Do I have to keep it up to date by hand?
No, and that is the design. The agent reads an item at the start of the work and writes back at the end of it, so the record is a byproduct of doing the work rather than a second job.
Is it tied to Claude?
No. It is an MCP server, so any client that speaks the Model Context Protocol can use it. Claude Code is where it gets used hardest, because that is where it was built.
What is the difference between the protocol and the cloud service?
The protocol is open source and you can run it yourself. The cloud service is the same thing without the setup, hosted, with an account and a token.
Get Work Context Protocol
Get updates
Occasional notes on what's happening at Enginery. No spam, no marketing.