Cmcp MCP Server

Client-Tool-Execution MCP Server. Exposed over MCP by the cmcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

The server acts as a proxy and registry - it has no predefined tools and simply routes execution to clients:

• ❌ Server needs access to all resources (files, DOM, APIs)
• ❌ Security concerns with server-side execution
• ❌ Limited to server environment capabilities
• ✅ Client has natural access to its own environment (DOM, local files, etc.)
• ✅ Better security - no need to expose sensitive resources to server
• ✅ Scalable - each client handles its own execution load

Adding it to your client

@mcpc-tech/cmcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• Installation — The Installation tool exposed by this server

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cmcp mcp server does with a few real requests.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cmcp's toolset — Installation — is a fair guide to whether it matches your workflow. It is maintained by yaonyan; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.