Work Context Protocol

io.workcontextprotocolPublished by workcontextprotocol.ioOfficial publisherv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote MCP server that gives an AI assistant persistent work tracking for tasks, status and history across machines.

What you can do
Work Context Protocol is a hosted, remote MCP endpoint. According to its registry description, it provides persistent work tracking for AI agents: tasks, their status, and history that follow the user across machines. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant's task list and progress to persist between sessions and devices rather than living in a single conversation or machine.
Requirements
A remote MCP client connecting to the hosted endpoint over streamable HTTP. Authentication is required via OAuth. No packages, environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, so an account and authorization grant are involved. Task and history data is stored on a third-party hosted service rather than locally. No tool list is published, so review what it can read or change before connecting.

Installation

In SourceWeft

  1. Open Work Context Protocol in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.workcontextprotocol%2Fwcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "work-context-protocol": {
      "type": "http",
      "url": "https://workcontextprotocol.io/mcp?src=registry"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.