Skip to main content

​
Before you start

You need an API key and the MCP endpoint shown in Jolts’ connection guide. Use the company-data endpoint, not this documentation site’s /mcp search server. An active or trialing subscription is required for company operations, but not tool discovery.

​
Configure your client

Merge this into your project’s .mcp.json. Replace YOUR_MCP_ENDPOINT with the endpoint copied from Jolts. The key stays in an environment variable rather than in the file:
In Bash, enter the key without putting it in shell history, then start Claude Code:
Review the project server approval, then open /mcp and check Jolts’ connection and tools. This configuration is for Claude Code, not a universal Claude Desktop or claude.ai connector. See Claude Code’s MCP configuration.

​
Verify before searching

Ask your assistant to list the Jolts tools without running a search. Expect search_companies, get_companies, and get_usage. Then ask it to call get_usage without arguments to inspect your allowance. That read is unmetered. Next, try a company-research workflow. Review the tool approval first: searches and known-company lookups consume your account’s allowance.

​
Troubleshooting

  • No tools: check the endpoint, client trust approval, and workspace policies.
  • Unauthorized: check that the bearer header is sent; never paste a key into chat.
  • Old tool names: reconnect or refresh discovery after upgrading.
  • Tools work but searches fail: read the structured error; check subscription and limit errors.
Return to all setup options or inspect the tool reference.