Pulse Subregistry
Browse and discover MCP servers from the PulseMCP Sub-Registry inside your agent when you are assembling or scoping an MCP stack.
Overview
Pulse Subregistry is an MCP server for the Build phase that lets your agent browse and discover MCP servers via the PulseMCP Sub-Registry.
What is this MCP server?
- Query PulseMCP Sub-Registry for MCP server discovery from the agent
- Authenticated access via PULSEMCP_SUBREGISTRY_API_KEY
- Multi-tenant support with PULSEMCP_SUBREGISTRY_TENANT_ID
- SHOW_ADMIN_TOOLS flag (default false) for switch_tenant_id and admin tools
- Productionized package @pulsemcp/pulse-subregistry 0.0.7 stdio npm
- Package version 0.0.7 (@pulsemcp/pulse-subregistry)
- SHOW_ADMIN_TOOLS defaults to false
- Repository path: productionized/pulse-subregistry on pulsemcp/mcp-servers
Community signal: 70 GitHub stars.
What problem does it solve?
Choosing MCP servers from scattered lists and bookmarks wastes time when you are trying to scope or wire an agent workspace.
Who is it for?
Builders actively curating MCP stacks who already have PulseMCP sub-registry access.
Skip if: Anyone who needs a public directory with no API key or who wants deep security audit data inside the same tool.
What do I get? / Deliverables
Your agent can query a curated sub-registry so shortlists and comparisons happen in-thread before you install individual MCP servers.
- In-agent browse and search results from PulseMCP Sub-Registry
- Tenant-scoped discovery when TENANT_ID is set
- Optional admin tenant switching when SHOW_ADMIN_TOOLS is true
Recommended MCP Servers
Journey fit
Server discovery is most actionable while building agent tooling, but the same registry answers early discover and validate scoping questions. Agent-tooling is where you pick which MCP servers to install; sub-registry access is the catalog layer for that decision.
How it compares
Registry discovery MCP bridge, not a marketplace checkout or a single-purpose integration server.
Common Questions / FAQ
Who is Pulse Subregistry for?
Solo builders and small teams using MCP agents who want in-editor discovery of MCP servers from PulseMCP’s sub-registry.
When should I use Pulse Subregistry?
Use it during build/agent-tooling—or earlier discover/scope—when you need to find and compare MCP servers before adding them to your config.
How do I add Pulse Subregistry to my agent?
Configure stdio @pulsemcp/pulse-subregistry with npx -y, set PULSEMCP_SUBREGISTRY_API_KEY, optional tenant ID, set SHOW_ADMIN_TOOLS only if needed, then reload MCP.