// mcp/roo-code/

How do I add ToolForte to Roo Code?

Add the server to Roo Code's mcp_settings.json, or to a .roo/mcp.json in the project, with the streamable-http type and the server URL. Roo connects and lists the tools in its MCP panel.

Step by step

The server URL is https://toolforte.com/api/mcp. Nothing runs on your machine; the client connects to it over streamable HTTP.

  1. 01
    Open the MCP settings
    Click the MCP Servers icon in the Roo Code panel and choose Edit Global MCP, or Edit Project MCP for one project.
  2. 02
    Paste the server
    Add the configuration below and save. Roo connects at once and shows the tools under the server.
  3. 03
    Try a tool
    Ask: "Validate the IBAN NL91 ABNA 0417 1643 00 with ToolForte."

Configuration

Roo Code reads its MCP servers from mcp_settings.json (global) or <project>/.roo/mcp.json.

mcp_settings.json
{
  "mcpServers": {
    "toolforte": {
      "type": "streamable-http",
      "url": "https://toolforte.com/api/mcp"
    }
  }
}
mcp_settings.json with an API key
{
  "mcpServers": {
    "toolforte": {
      "type": "streamable-http",
      "url": "https://toolforte.com/api/mcp",
      "headers": {
        "Authorization": "Bearer tf_your_key_here"
      }
    }
  }
}

Adding an API key

Does a key work in Roo Code?
Yes: a headers object in mcp_settings.json. Everything below applies.

Add a headers object next to the url, as in the second snippet. Use the global file for anything with a key in it, so it stays out of the repository.

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.

Free or paid: what changes

Without a key the server answers initialize, tools/list, prompts and resources, and it will search and describe tools, but it runs nothing else. AI tools and renders never run without a key. A key, free or paid, sets how much of the server-side work you can do in a month; the free one is a trial. A tool call costs 1 credit, a render 25; memory is free.

Without a keyFree keyToolForte Pro
PriceNothingNothing€19.00 a month, or €190.00 a year
Utility toolsListed and described, not run100 credits a month, so up to 100 calls7,500 credits a month, so up to 7,500 calls
Renders (PDF, screenshot, read_page)Refused: every call needs a keyUp to 4 a month from the same balanceUp to 300 a month from the same balance
Agent memoryRefused: needs a key, so entries have an ownerPrivate to your key, kept 30 days, never meteredPrivate to your key, kept 365 days, never metered
Saved workflows (workflow_run)Refused: a workflow belongs to an accountYes, each step costs what its tool costsYes, each step costs what its tool costs
Usage historyNone7 days365 days
When the month runs outNot applicable: a tool that does work needs a keyBuy credits from 100 for €1.00, they never expire, or move to ToolForte ProBuy credits from 100 for €1.00, they never expire

The same balance also pays for the REST API and the AI tools, and every tool result tells the assistant what is left. When it is gone the call is refused with a plain message; nothing keeps running on credit. Full detail on pricing and credits and plans.

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 Roo Code 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 Roo Code.

Check that it works

One question is enough to see the server answer instead of the model.

Ask the assistant
Validate the IBAN NL91 ABNA 0417 1643 00 with ToolForte.
What a correct answer looks like
The assistant calls validate_iban and reports the result of the mod-97 check and the bank country. If it answers without calling a tool, the server is not connected yet: look for it in the client's MCP or connector list and make sure it is switched on for the conversation.

Questions

The Roo Code specifics first, then what applies to every client.

Which tools should I allow automatically?

The deterministic utilities only compute an answer, so auto-approving them saves a click per call and risks nothing. Keep approval on for renders, which spend credits, and for the memory tools, which write.

What does the ToolForte MCP server cost?

The 150 deterministic utilities can be listed and described freely. search_tools and describe_tool run without a key; every other tool call needs an API key. AI tools and renders never run without one. The free account is a trial of 100 credits a month: a tool call costs 1 credit and a render 25, so that is 100 calls or 4 renders. 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. You never have to guess: every tool in the list carries its price, and every result says what the call cost and what is left.

Do I need an API key?

Not to connect. initialize, tools/list, prompts and resources work without a key, and so do search_tools and describe_tool. Every other tool call needs one, and the refusal says how to get it (api_key_required, or HTTP 401 with the same instructions when the client can sign in). AI tools and renders never run without one. You create a key on your ToolForte account page, or with POST https://toolforte.com/api/v1/keys/bootstrap and {"email"} from a script, which emails the key to that address, and pass it as an Authorization: Bearer header; an X-API-Key header works too.

Which tools does the server expose?

180 tools in four groups: 150 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).

Why does my client list only a handful of tools?

On purpose. A session that loads all 180 tool definitions spends tens of thousands of tokens before the first message, and models choose worse from a long list, so the plain URL lists a small core plus three meta tools: search_tools finds any tool by a word from the job, describe_tool returns its full schema, and run_tool runs it by name. Every tool stays callable by name as well. To list everything up front, connect to https://toolforte.com/api/mcp?tools=all; to pick jobs, use ?tools=pdf,dutch or any names, comma separated. With the npm bridge, set TOOLFORTE_TOOLS.

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.

What you can ask once it is connected

The server answers to 180 tool names. The full list, grouped and explained, is on the MCP page.

Check an IBAN or a VAT number, compute VAT on an amount, count working days between two dates in the Netherlands, explain a cron expression, test a regex, format or diff JSON, turn an HTML report into a hosted PDF, screenshot a page, read a JavaScript-rendered page as Markdown, remember something for next week, or run a saved workflow by id. See every tool.

Other clients
The MCP server
Every tool the server exposes, what each one costs, and the endpoint itself.
Claude
How do I add ToolForte to Claude?
Claude Code
How do I add ToolForte to Claude Code?
Cursor
How do I add ToolForte to Cursor?
VS Code
How do I add ToolForte to VS Code and GitHub Copilot?
ChatGPT
How do I add ToolForte to ChatGPT?
Windsurf
How do I add ToolForte to Windsurf?
Gemini CLI
How do I add ToolForte to Gemini CLI?
Codex CLI
How do I add ToolForte to Codex CLI?
Cline
How do I add ToolForte to Cline?
Continue
How do I add ToolForte to Continue?
OpenCode
How do I add ToolForte to OpenCode?
Zed
How do I add ToolForte to Zed?
the Anthropic API
How do I add ToolForte to the Anthropic API?
the OpenAI Agents SDK
How do I add ToolForte to the OpenAI Agents SDK?
the Vercel AI SDK
How do I add ToolForte to the Vercel AI SDK?
LangChain
How do I add ToolForte to LangChain?