hockeystack-revenue-agents-mcp package exposes the full Revenue Agents
v1 API surface — agents, conversations, tasks, and credits — as Model Context
Protocol tools. Drop it into any MCP-compatible client to let an LLM drive the
API directly.
Prerequisites
- Node.js 18 or newer.
- A Revenue Agents API token. Generate one in the HockeyStack workspace
settings. Tokens look like
hsr_live_<hex>.
Run
Run directly withnpx — no install step:
Configure
The server reads configuration from environment variables.| Variable | Required | Default |
|---|---|---|
HOCKEYSTACK_API_TOKEN | Yes | — |
HOCKEYSTACK_BASE_URL | No | https://app.hockeystack.com/api/revenue-agents/v1 |
Add to your MCP client
The configuration is the same across MCP clients — only the config file location differs.- Claude Desktop (macOS):
~/Library/Application Support/Claude/claude_desktop_config.json - Claude Desktop (Windows):
%APPDATA%\Claude\claude_desktop_config.json - Cursor: Settings → MCP, or
~/.cursor/mcp.json - Claude Code:
~/.claude.jsonundermcpServers
Tools exposed
Each tool maps one-to-one to a Revenue Agents API endpoint. Tool names are prefixed withhs_.
Service
hs_health— Liveness probe (unauthenticated).hs_me— Token introspection.
hs_list_company_agents,hs_init_company_agent,hs_get_company_agent,hs_delete_company_agenths_list_deal_agents,hs_init_deal_agent,hs_get_deal_agent,hs_delete_deal_agent
hs_create_deal_conversation,hs_list_deal_conversations,hs_delete_deal_conversationhs_list_deal_conversation_messages,hs_send_deal_message
hs_create_company_conversation,hs_list_company_conversations,hs_delete_company_conversationhs_list_company_conversation_messages,hs_send_company_message
hs_list_tasks,hs_get_task,hs_create_task,hs_update_task,hs_delete_task
hs_credits_balance,hs_credits_usage,hs_credits_operations
Verify the connection
After restarting your client, ask it something that exercises the server:“Use the hockeystack tools to check my credit balance.”The client should call
hs_credits_balance and return the current usage
against your monthly bundle.
Troubleshooting
- Tools don’t appear: confirm the client picked up the new config — most clients require a full restart, not a window reload. Check the client’s MCP logs for spawn errors.
- Every call returns 401: the token is missing, malformed, or revoked.
Verify the value of
HOCKEYSTACK_API_TOKENand that it starts withhsr_live_. - 503 on message sends: the workspace has hit its monthly credit cap. See
Credits (
hs_credits_balance) to confirm.