Work Context Protocol
Every session starts
from scratch.
Unless you have WCP.
Your agent picks up where you left off and drives what's next.
Works with:
Not sure which tool you're using? Claude Cowork is the web app at claude.ai. Claude Code is the CLI tool for your terminal. Cursor is an AI code editor.
Setting up WCP with Claude Cowork
- 1 Open Settings → Connectors in Claude Cowork
- 2 Click Add custom connector and paste the URL below
- 3 Done — your agents now have persistent memory
https://workcontextprotocol.io/mcpEmerson McCuin
“I just do the work and the work is tracked for me.”
“I don’t ever experience analysis paralysis. I just say ‘what’s next’ and it gives me a list. I say ‘let’s go.’ No stress, just do.”
Onboarding his entire org to Claude
April Lutheran
“I constantly have to tell chat to look at other chats in our project.”
First MCP install ever. Built a kanban board from WCP data in minutes.
John S
“I started using WCP for the ‘what should we work on today’ prompt. Every session just picks up where I left off.”
Daily workflow at HaasAlert
“Where did we leave off?”
You don’t ask that anymore. Your agent already knows.
“What’s the status of this project?”
Your agent reads it from WCP before you finish typing.
“I just had an hour-long meeting.”
Claude extracted every action item into WCP with full context. No notes app required.
“I need to context-switch.”
Already loaded. Same session, different namespace.
Individual developers
Your agent picks up where it left off. Status, decisions, and history across every session.
Teams
Stop telling chat to look at other chats. One shared workspace your whole team’s agents can read and write.
Multi-project builders
Namespaces keep projects isolated. Switch contexts without losing context.
Open source. MIT-licensed. Migrate between cloud and self-hosted anytime.
Work metadata only. Titles, status, comments. No source code, no filesystem access.
Built by Dave Paola. Pittsburgh, PA.