pulsemcp-mcp.yml

PulseMCP authors and maintains 32 MCP servers — 4 "productionized" under the @pulsemcp/ npm scope and 28 "experimental" under unscoped npm names. EVERY ONE OF THEM IS A LOCAL STDIO SERVER distributed as an npm package. PulseMCP operates NO hosted/remote MCP endpoint of its own: there is no mcp.pulsemcp.com, and https://api.pulsemcp.com/mcp returns the API's JSON 404 (invalid_path). An agent cannot reach PulseMCP over MCP without a human first installing a package on a machine. The one server that fronts PulseMCP's OWN product is @pulsemcp/pulse-subregistry, an stdio wrapper over the PulseMCP Registry API at https://api.pulsemcp.com/v0.1. Its three tools are bound to the REST surface in mcp/pulsemcp-tool-crosswalk.yml. The other 31 servers wrap third-party products (Gmail, Slack, Vercel, 1Password, Fly.io, AWS, …) and are first-party PulseMCP code but not a PulseMCP API surface.

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.