MCP server

The Pulse MCP server is a small stdio process that turns the JSON API into eight read-only tools. Your agent can then screen tokens, inspect a wallet or read the latest newsletter without you pasting data.

How it works#

pulse-mcp does not open the database. It calls the Pulse HTTP API, so a Pulse instance must be running and reachable. Start one with npx -y -p pulse-trenches pulse (see Getting started) and point the MCP server at it with PULSE_URL.

• Transport: stdio. The client launches the process.
• Server name and version: pulse, 0.1.0.
• Read-only: every tool is annotated readOnlyHint: true and openWorldHint: false. Nothing writes to the archive or calls out to the internet.
• Output: each tool returns the API's JSON as text.

Tools#

Enumerated inputs (chain, status, sort, table) are validated with zod before the request is made, so a model that guesses a wrong value gets a clear schema error instead of an empty result.

Configuration#

Client setup#

All three clients take the same server entry. The -p pulse-trenches form is needed because the package ships two commands.

{
  "command": "npx",
  "args": ["-y", "-p", "pulse-trenches", "pulse-mcp"]
}

Claude Desktop#

Open Settings, Developer, Edit Config, and add the server to claude_desktop_config.json. Restart Claude Desktop.

{
  "mcpServers": {
    "pulse": {
      "command": "npx",
      "args": ["-y", "-p", "pulse-trenches", "pulse-mcp"],
      "env": { "PULSE_URL": "http://localhost:8787" }
    }
  }
}

Claude Code#

Add it from the command line, or commit a .mcp.json with the same mcpServers block as above.

claude mcp add pulse --env PULSE_URL=http://localhost:8787 -- npx -y -p pulse-trenches pulse-mcp

Cursor#

Put the block in ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one project.

{
  "mcpServers": {
    "pulse": {
      "command": "npx",
      "args": ["-y", "-p", "pulse-trenches", "pulse-mcp"],
      "env": { "PULSE_URL": "http://localhost:8787" }
    }
  }
}

Any other MCP client#

Run the command npx -y -p pulse-trenches pulse-mcp over stdio with PULSE_URL in its environment. From a source checkout, node src/cli.ts mcp does the same.

Try it#

Once connected, ask in plain language:

• "Use Pulse to list running tech tokens on Solana with at least $250K market cap."
• "Show me the latest Pulse newsletter and summarize what changed since yesterday."
• "Which smart wallets bought this token early?" (give the mint address)

When Pulse is not running#

If the API is unreachable, every tool fails with a message that tells the agent what to do: Cannot reach Pulse at ... Start it with "npx pulse-trenches" or set PULSE_URL. Start Pulse, or correct PULSE_URL, and call the tool again.