Your runtimes.
One working system.

Find skills, share configuration, and coordinate native AI runtimes. Keep the CLI you trust. Give it a shared workspace.

Claude · Codex · Gemini · Grok Build · Antigravity

A shared project, native sessions Interactive concept

* Mailbox is optional. Interactive Three.js scene; no runtime is connected.

One project.
A clearer way to work.

Start with skill discovery. Add a shared configuration. Coordinate sessions when you need them.

1

Discover

Find the skill that fits your next task, then read its instructions.

skill_find → skill_read
2

Configure

Keep common MCP settings in pmcp.toml and project them to your tools.

pmcp project
3

Coordinate

Use optional mailbox and owned sessions without replacing native approvals.

mailbox + harness + tui

Keep the runtime.
Connect the work.

A main session leads. Workers keep their native tools. PMCP supplies the shared layer underneath.

pmcp tui / project workspaceIllustrative layout
MAIN · Codex · native terminal

› Review the release plan with the workers.

I’ll ask a worker to inspect configuration, then compare the results.

The provider conversation remains in its own runtime.

›
WORKERS

config-review
Native session · example

test-review
Native session · example

Inspect before sending input.

MAILBOX / optional

config-review → main   “Configuration reviewed.”

OAuth, folder trust, and tool approvals stay with each native runtime.

Explore the optional session layer

A small core.
Room to grow.

Use what your project needs. Skill discovery works without an embedding model or a session manager.

Core

Find instructions that fit the task.

Search workspace and plugin skills. Read a SKILL.md before using it. Lexical discovery works without a model download.

skill_find → skill_read

Task: review release readiness
Source: workspace or plugin catalog
Read the guide

The right skill.
At the right moment.

Search by the task you want to finish.
Inspect the instructions before you use them.

Package-specific skills are free to read, download and use without login.

Browse free package skills

From install
to shared workspace.

Choose a runtime. Add PMCP to your project. Review generated changes before applying them.

Node.js 22+ or Bun 1.3+ for the core package.
Terminal / project root
npm install --save-dev @modootoday/pmcp

Node.js 22+ or Bun 1.3+. Your runtime keeps its existing authentication.

Open the complete setup guide

Your tools.
Your boundaries.

Shared infrastructure should make the working model easier to understand.

Does PMCP replace my AI runtime?

No. Your native runtime makes model requests and handles its own authentication. PMCP provides discovery, shared configuration, and optional coordination tools.

Do I need mailbox, a terminal host, or embeddings?

Skill discovery and shared configuration do not require them. Mailbox and semantic search are optional. The optional harness and TUI need Linux (glibc 2.35 or later) with a user systemd manager, or macOS; npm installs pmcp-pty and pmcp-tui with pmcp.

Can MCP clients run the session manager?

Session execution belongs to the optional CLI host. It is separate from the MCP server execution boundary.

What is the license?

PMCP is source available under Elastic License 2.0. Read the license before redistributing or offering a hosted service.

Make it fit
your project.

Native tools.
Shared possibilities.

Build your shared workspace