How do I add ToolForte to Claude?

https://toolforte.com/api/mcp/mcp

{
  "mcpServers": {
    "toolforte": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://toolforte.com/api/mcp/mcp"
      ]
    }
  }
}

Adding an API key

With a custom connector there is no header field yet, so the free utilities and 3 renders a day are what you get. Through the desktop bridge, add "--header" and "Authorization: Bearer tf_your_key_here" to the args array and the key travels with every call.

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.

Why do I not see Add custom connector?

Custom connectors are available on the Pro, Max, Team and Enterprise plans. On the free plan, use the desktop app with the bridge configuration on this page.

Which Claude tool names should I expect?

Tools like validate_iban, calculate_vat, working_days_between, html_to_pdf and memory_set. Claude shows them under the connector and picks one when your question needs it.

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.