pulse-subregistry — Claude Code MCP server: setup and overview
Connects your assistant to the PulseMCP Sub-Registry catalog to search and inspect MCP servers. Useful when finding existing tool integrations directly from chat.
claude mcp add --env PULSEMCP_SUBREGISTRY_API_KEY=<PULSEMCP_SUBREGISTRY_API_KEY> --env PULSEMCP_SUBREGISTRY_TENANT_ID=<PULSEMCP_SUBREGISTRY_TENANT_ID> --env SHOW_ADMIN_TOOLS=<SHOW_ADMIN_TOOLS> --transport stdio pulse-subregistry -- npx -y @pulsemcp/pulse-subregistryWhat pulse-subregistry does
The server links an assistant directly to the PulseMCP Sub-Registry directory. You query available packages with list_servers, using pagination cursors and search filters by keyword or update date. Detailed package records come from get_server, which defaults to the latest release and returns repository links alongside metadata. The switch_tenant_id tool stays hidden. Enabling it requires setting SHOW_ADMIN_TOOLS=true.
Output sizes stay under control. Responses truncate strings past 200 characters and collapse nested objects deeper than level five. To pull entire fields such as readmes, pass their paths into expand_fields. Node.js 18 or newer must be present on the host. Without a valid PULSEMCP_SUBREGISTRY_API_KEY, all catalog queries fail.
What it helps with
- Search MCP packages by keyword and title
- Fetch repository details and release versions for a chosen server
- Page through directory results using cursor-based pagination
- Filter registry listings by update timestamp
Example prompts for the agent
- Find all MCP servers related to GitHub in the registry.
- Get the latest details and repository link for
@anthropic/mcp-server-filesystem. - Fetch the next batch of servers using the pagination cursor from the last response.
How to install pulse-subregistry
Platform CLI
claude mcp add --env PULSEMCP_SUBREGISTRY_API_KEY=<PULSEMCP_SUBREGISTRY_API_KEY> --env PULSEMCP_SUBREGISTRY_TENANT_ID=<PULSEMCP_SUBREGISTRY_TENANT_ID> --env SHOW_ADMIN_TOOLS=<SHOW_ADMIN_TOOLS> --transport stdio pulse-subregistry -- npx -y @pulsemcp/pulse-subregistryReplace <…> with your own values
Platform CLI
codex mcp add pulse-subregistry --env PULSEMCP_SUBREGISTRY_API_KEY=<PULSEMCP_SUBREGISTRY_API_KEY> --env PULSEMCP_SUBREGISTRY_TENANT_ID=<PULSEMCP_SUBREGISTRY_TENANT_ID> --env SHOW_ADMIN_TOOLS=<SHOW_ADMIN_TOOLS> -- npx -y @pulsemcp/pulse-subregistryReplace <…> with your own values
Config file
{
"mcpServers": {
"pulse-subregistry": {
"command": "npx",
"args": [
"-y",
"@pulsemcp/pulse-subregistry"
],
"env": {
"PULSEMCP_SUBREGISTRY_API_KEY": "<PULSEMCP_SUBREGISTRY_API_KEY>",
"PULSEMCP_SUBREGISTRY_TENANT_ID": "<PULSEMCP_SUBREGISTRY_TENANT_ID>",
"SHOW_ADMIN_TOOLS": "<SHOW_ADMIN_TOOLS>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"pulse-subregistry": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pulsemcp/pulse-subregistry"
],
"env": {
"PULSEMCP_SUBREGISTRY_API_KEY": "<PULSEMCP_SUBREGISTRY_API_KEY>",
"PULSEMCP_SUBREGISTRY_TENANT_ID": "<PULSEMCP_SUBREGISTRY_TENANT_ID>",
"SHOW_ADMIN_TOOLS": "<SHOW_ADMIN_TOOLS>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e PULSEMCP_SUBREGISTRY_API_KEY=<PULSEMCP_SUBREGISTRY_API_KEY> -e PULSEMCP_SUBREGISTRY_TENANT_ID=<PULSEMCP_SUBREGISTRY_TENANT_ID> -e SHOW_ADMIN_TOOLS=<SHOW_ADMIN_TOOLS> pulse-subregistry npx -y @pulsemcp/pulse-subregistryReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about pulse-subregistry
How do I install pulse-subregistry in Claude Code?
Run claude mcp add pulse-subregistry -e PULSEMCP_SUBREGISTRY_API_KEY=<PULSEMCP_SUBREGISTRY_API_KEY> -- npx -y @pulsemcp/pulse-subregistry in your terminal, replacing <PULSEMCP_SUBREGISTRY_API_KEY> with your key.
What does pulse-subregistry do?
It provides tools for searching the PulseMCP Sub-Registry directory, checking server details, and retrieving repository links for MCP implementations.
Why are some text fields truncated in tool responses?
Strings over 200 characters are trimmed to conserve model context. Specify the desired property paths inside the expand_fields parameter to view the full content.
