Skip to main content

​
Configure the connection

Create a Jolts API key and copy the company-data MCP endpoint from Jolts’ connection guide. Merge this into your project’s .cursor/mcp.json:
Replace the endpoint placeholder. Set JOLTS_API_KEY in the environment that launches Cursor, then restart Cursor. Do not put the secret in this file, a prompt, or a screenshot. For an all-project connection, use ~/.cursor/mcp.json instead.
Cursor’s envFile setting applies to local STDIO servers, not remote HTTP servers. Putting a key in your project’s .env alone does not configure this connection.

​
Verify and use it

Enable Jolts in Cursor’s MCP settings and review any trust request. In Agent, ask to inspect Jolts’ tools without running a search. Expect search_companies, get_companies, and get_usage. Call get_usage without arguments first to check your allowance at no usage charge. Try researching known accounts or finding active demand. Review the tool call before approving: searches and company lookups consume your account’s shared allowance.

​
Troubleshooting

An authentication failure usually means Cursor cannot read the environment variable or the key was revoked. A connected server with unavailable tools may be restricted by organizational policy. A company-operation error is separate from connection setup; consult troubleshooting. Jolts does not currently offer OAuth login. See Cursor’s official MCP guide and the Jolts tool reference.