Cursor integration

What you get

Use Cursor with KeepBal discovery, inspection and paid tool execution through one key and prepaid wallet.

Prerequisites

Create a KeepBal account and API key. Signup includes $1 credit once. Keep the key private and ensure sufficient wallet credit before executing a tool.

Create an account · API keys

Setup

Install Cursor and make KEEPBAL_API_KEY available to the process launching it. Put this configuration in ~/.cursor/mcp.json globally or .cursor/mcp.json for a project.

{"mcpServers":{"keepbal":{"url":"https://keepbal.com/mcp","headers":{"Authorization":"Bearer ${env:KEEPBAL_API_KEY}"}}}}

Enable the server in Customize. Inspect the Output panel → MCP Logs if tools do not appear; confirm the environment variable is available to Cursor.

Cursor official documentation

Worked example: read a web page

Ask your agent: Find the page-content tool, inspect exa/contents, then fetch https://example.com with text enabled and summarize the result. Review the published price before approving execution. Data is from Exa; this does not imply partnership.

search_tools {"query":"page contents"}
inspect_tool {"tool":"exa/contents"}
run_tool {"tool":"exa/contents","input":{"body":{"urls":["https://example.com"],"text":true}}}

These are MCP tool names and argument objects. The client wraps them in tools/call requests. If run_tool returns pending with a run_id, call get_run {"run_id":"RETURNED_RUN_ID"}; do not repeat run_tool.

Troubleshooting

Initialization and tools/list work without a key; every tools/call requires a valid bearer key, including search and inspect. For 401 check the key and client launch environment. For insufficient_credits check Wallet; for rate_limited respect Retry-After. Check Usage after uncertain outcomes before retrying a paid call. Truncated or unsupported MCP results must not be retried.

Exa contents tool · Search and extraction tools · Errors · MCP reference · All integrations