How do I add ToolForte to Cursor?

{
  "mcpServers": {
    "toolforte": {
      "url": "https://toolforte.com/api/mcp/mcp"
    }
  }
}

{
  "mcpServers": {
    "toolforte": {
      "url": "https://toolforte.com/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer tf_your_key_here"
      }
    }
  }
}

Adding an API key

Add a headers object next to the url, as in the second snippet. Cursor sends the header on every request.

A key starts with tf_ and is created on your account page. It is free, and it is what gives memory a private owner and workflows an account to run on.

Validate the IBAN NL91 ABNA 0417 1643 00 with ToolForte.

The install button does nothing. What now?

The link uses the cursor:// scheme, which only works when Cursor is installed on the machine you are browsing from. Paste the mcp.json configuration instead; the result is the same.

Does Cursor ask before every tool call?

By default yes: agent mode shows the call and waits for approval. You can allow a server automatically in the MCP settings if you prefer.

What does the ToolForte MCP server cost?

The 23 deterministic utilities are free and so is agent memory. Each client session gets 3 renders a day without a key. A free API key adds 1,000 credits a month for renders and workflows, and a paid plan raises that.

Do I need an API key?

Not for the utilities. A key is what makes memory private to you, gives access to the workflows on your account, and moves renders onto a monthly balance instead of the daily allowance. You create one on your ToolForte account page and pass it as an Authorization: Bearer header.

Which tools does the server expose?

35 tools in four groups: 23 deterministic utilities such as validate_iban, calculate_vat, working_days_between, parse_cron and test_regex; 6 render tools (html_to_pdf, url_to_pdf, url_screenshot, qr_code_png, pdf_merge, read_page) that return hosted files or page content; 4 memory tools (memory_set, memory_get, memory_list, memory_delete); and 2 workflow tools (workflow_list, workflow_run).

Is what I send to a tool stored?

Tool inputs are processed on ToolForte servers and not kept, except for the memory tools, whose entire purpose is to keep what you store, and rendered files, which are hosted for 24 hours behind a signed link. The browser tools on toolforte.com never send anything; the MCP server necessarily does.

Is there anything to install?

No. The server runs at toolforte.com and every client on this page connects to it over streamable HTTP. The only exception is the free Claude desktop plan, which needs a small bridge started with npx.