PCD (Portable Context Deck)

ai.portablecontextPublished by portablecontext.aiOfficial publisherv0.4.0Updated Oct 24, 2026

Your portable context layer — load it into any AI.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

PCD gives an assistant a portable, account-hosted context layer of containers, work state, knowledge, signals, and skills loaded over one MCP endpoint.

What you can do
PCD (Portable Context Deck) is a remote MCP server that briefs an AI client with your own structured context. A single load call brings in your operating context, and you can load the console to create and manage containers, load a specific container, or load a specialist scoped to a domain, role, or task. It also carries live work state, accumulated knowledge, signals that outlive a session, reusable skills, and experimental connections to external tools through one authenticated surface.
When to use it
Worth adding if you work across several MCP-capable clients, such as a desktop app, an IDE, and chat, and want the same briefing, work state, and knowledge to follow you instead of being rebuilt per client. It suits people who want to organize context into containers and specialists rather than repeat setup each session.
Requirements
A remote Streamable HTTP endpoint at reachable over the network. An account is required; access is in early access with self-serve signup in controlled batches. Sign-in happens on first connect using OAuth 2.0 with PKCE, and no API key is required. A web dashboard is available for managing containers and connections.
Before you install
Your context, work state, and knowledge are stored in your PCD account on a third-party service, so anything you load is sent to that provider; the README states data is not sold or trained on, but you should judge what is appropriate to place there. Connections to external tools are described as experimental, so treat them as less settled. Sign-in uses OAuth 2.0 with PKCE and no API key.

Installation

In SourceWeft

  1. Open PCD (Portable Context Deck) 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/ai.portablecontext%2Fpcd/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": {
    "pcd-portable-context-deck": {
      "type": "http",
      "url": "https://mcp.portablecontext.ai/mcp"
    }
  }
}

README

PCD — Portable Context Deck

Your context. Any AI.

PCD is your portable context layer. Connect an MCP-capable client to one endpoint and it boots with your containers: structured context, live work state, and accumulated knowledge, composed by you and carried across every client you use. Use it in whichever AI you're working in—desktop, IDE, or chat—each already briefed, with nothing tied to a single client.

Access

PCD is in early access, with self-serve signup available in controlled batches. Go to app.portablecontext.ai to create an account when capacity is available.

If the current batch is full, you can leave your email there and we'll be in touch when capacity opens.

An account gives you the full product setup: an MCP endpoint for any compatible client, a web dashboard with a live view of your containers—skills, knowledge, signals, and work—plus connection management and export. The documentation is public.

Connect

Once you're in, point an MCP-capable client at the endpoint and sign in on first connect. No API key is required.

Endpointhttps://mcp.portablecontext.ai/mcp
TransportStreamable HTTP
AuthenticationOAuth 2.0 + PKCE
json
{  "mcpServers": {    "pcd": {      "url": "https://mcp.portablecontext.ai/mcp",      "transport": "http"    }  }}

Then load console to create and manage your containers, load <container> to enter one, or load a specialist directly.

What you get

  • Load — one call briefs your AI with your operating context.
  • Specialists — specialized contexts scoped to a domain, role, or task.
  • Work state — live work that follows you across clients.
  • Knowledge — your accumulated, structured understanding.
  • Signals — findings that outlive a session.
  • Skills — reusable skills attached to a deck or shared across them.
  • Connections (experimental) — connected external tools through one authenticated surface.

Data and privacy

Your data stays in your account—we don't sell it or train on it.

Source and licence

This repository contains PCD's public core under the GNU Affero General Public License v3.0 only. The mechanism is open and inspectable—AGPL guarantees it stays that way.

This source snapshot is not currently packaged as a runnable self-hosted distribution. A community self-hosted edition is on the table when demand justifies it. PCD's managed service, operational layer, and private product capabilities are not part of this repository.

The bundled fonts keep their upstream licences; see Third-party notices. PCD's names, logos, and brand assets are handled separately; see Trademarks.

Contributions

External code contributions are not currently accepted. Before opening contributions, PCD will publish a contributor licence agreement that explains the rights needed to maintain both the open-source and possible commercial licensing paths.

PCD-### references in code comments point to the project's internal issue tracker and are kept as provenance markers.

Built with PCD, inside PCD.

Source: README.md at commit 32a9892

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. v0.4.0LatestSep 16, 2026

Score

85% 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
  • Documentation15 pts
  • License10 pts