How do I add ToolForte to Cursor?

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

{
  "mcpServers": {
    "toolforte": {
      "url": "https://toolforte.com/api/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.

From free to paid, in order

1. Create a free account. An email address is all it asks for.
2. On your account page, create an API key. It is shown once; copy it then.
3. Put the key in Cursor as described above, and restart or refresh the connection.
4. Ask for something server-side, such as a PDF. The result names your remaining balance, which proves the key arrived.
5. Running low? Buy credits on the pricing page, or take ToolForte Pro there for the larger monthly balance. Both use the same key; nothing changes in Cursor.

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 84 deterministic utilities are free and so is agent memory. Each client session gets 3 renders a day without a key. With a free API key you get a monthly balance of 1,000 credits: a tool call costs 1 credit and a render 25, so that is 40 renders or 1,000 calls. ToolForte Pro is €19.00 a month for 7,500 credits, and any account can buy extra credits from 100 for €1.00 that never expire.

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; an X-API-Key header works too.

Which tools does the server expose?

111 tools in four groups: 84 deterministic utilities such as validate_iban, calculate_vat, working_days_between, parse_cron and test_regex; 14 render tools (html_to_pdf, url_to_pdf, url_screenshot, qr_code_png, pdf_merge, pdf_split, images_to_pdf, image_resize, image_convert, image_compress, read_page, strip_metadata, pdf_to_docx, docx_to_pdf) that return hosted files or page content; 4 memory tools (memory_set, memory_get, memory_list, memory_delete); and 3 workflow tools (workflow_list, workflow_run, workflow_propose).

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. A client that only speaks stdio, such as the Claude desktop app on the free plan, runs "npx -y toolforte-mcp" instead: a small bridge on npm that connects to the same server.