Give Claude Code & Cursor 313+ Tools with One API Key
Connect Claude Code, Cursor, or Claude Desktop to https://helve.dev/mcp once. Your agent gets on-demand discovery and pay-per-call execution across 313+ live APIs with zero OAuth flows and zero context bloat.
1. Claude Code Setup
Add Helve as a Streamable HTTP MCP server in one command:
claude mcp add --transport http helve https://helve.dev/mcp --header "Authorization: Bearer sk_live_YOUR_KEY"
2. Cursor Setup (~/.cursor/mcp.json)
{
"mcpServers": {
"helve": {
"type": "http",
"url": "https://helve.dev/mcp",
"headers": {
"Authorization": "Bearer sk_live_YOUR_KEY"
}
}
}
}
3. Claude Desktop Setup
Add the same mcpServers.helve block to claude_desktop_config.json, or point any MCP-compatible client at https://helve.dev/mcp.
4. Why Dynamic Tool Search Avoids Context Bloat
Loading 250+ raw tool schemas into every prompt wastes tens of thousands of tokens. Helve exposes 11 compact MCP tools (search_tools, list_categories, call_tool, get_balance, request_tool, plus transcription helpers) so your agent fetches only the exact schema it needs at runtime.
Need a hard budget guardrail? Set spend_limit_usd on your API key in the dashboard so runaway loops stop deterministically at your limit.
Get API Key ($0.50 Free) Browse All 313 Tools
FAQ
Connect Claude Code, Cursor, or Claude Desktop to Helve's single Streamable HTTP MCP server (https://helve.dev/mcp) with one Bearer API key (sk_live_...). Your agent discovers tools on demand via search_tools and executes them via call_tool without vendor signups or OAuth flows.
Instead of registering 250 separate MCP tools in tools/list, Helve exposes 11 compact meta-tools (search_tools, list_categories, call_tool, get_balance, request_tool, and transcription helpers). The agent searches only for the tools it needs right now.
Yes. Every Helve API key supports a deterministic spend_limit_usd cap that blocks calls with HTTP 402 spend_limit_exceeded before any upstream provider is contacted.