Fuentio MCP in Cursor and VS Code: Step-by-Step Setup

Cursor and VS Code both run AI agents that can call tools over MCP, the Model Context Protocol. Add Fuentio and the agent in your editor can look up, search and verify French and Spanish companies from official registers: while it writes an import script, cleans a fixture file or answers a question about a supplier.

This tutorial covers both editors: the one-click install, the JSON file if you prefer to write it yourself, how to add an API key without committing it, how to check the tools are there, and a first prompt.

What you'll learn

• The one-click install for each editor
• The mcp.json file for Cursor, and the .vscode/mcp.json file for VS Code
• How to add your key without putting it in the repository
• How to check that the server and its 17 tools are available
• A first prompt and what the agent receives

The address

Both editors connect to the same address, over streamable HTTP:

https://api.fuentio.com/mcp

No key is needed to start: Fuentio runs on the keyless trial (20 units a day), and listing the tools is free. A free key gives 100 units a month and unlocks the tools that need one.

Cursor

One click

On the connect page, open the Cursor tab and press Add to Cursor. Cursor opens and asks you to confirm the new server.

Or the JSON file

Add Fuentio to ~/.cursor/mcp.json (all your projects) or .cursor/mcp.json (one project):

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

With a key, add an authorization header:

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

Keep the version with the key in your global file (~/.cursor/mcp.json), not in a project file you commit. A project file without a key is safe to share: everyone starts on the keyless trial.

Check it

Open Cursor's settings and find the MCP section: Fuentio should be listed and enabled, with its tools. Then use the agent in chat and ask a question; Cursor shows the tool call before running it.

VS Code

In VS Code, the agent in the chat (agent mode) is what calls MCP tools.

One click

On the connect page, open the VS Code tab and press Add to VS Code. VS Code opens and offers to install the server.

Or the JSON file

In your project, create .vscode/mcp.json:

{
  "servers": {
    "fuentio": {
      "type": "http",
      "url": "https://api.fuentio.com/mcp"
    }
  }
}

A key without committing it

VS Code can prompt for a secret the first time the server starts and keep it outside the file. Declare an input and reference it in the header:

{
  "inputs": [
    { "type": "promptString", "id": "fuentio-key", "description": "Fuentio API key", "password": true }
  ],
  "servers": {
    "fuentio": {
      "type": "http",
      "url": "https://api.fuentio.com/mcp",
      "headers": { "Authorization": "Bearer ${input:fuentio-key}" }
    }
  }
}

This file is safe to commit: it contains no key. Each developer types their own the first time.

Check it

Run MCP: List Servers from the command palette: Fuentio should be listed and running. In the chat, use agent mode and select Configure Tools in the chat input: Fuentio's tools appear there, and you can turn individual tools on or off.

A first prompt

In either editor, ask the agent:

"Is SIREN 441639465 still active? Quote the source."

The agent calls lookup_company(country="FR", identifier="441639465"). The first line of what it receives, recorded on 12 October 2026:

RENAULT (FR, SIREN 441639465) is active as of 2025-12-06, source: Annuaire des Entreprises (API Recherche d'entreprises).

The full structured record follows, so the agent can answer follow-up questions (address, legal form, activity, identifiers) without another call. For Spain, ask by name: "Find Mercadona in Spain" calls search_companies(country="ES", query="mercadona") and returns MERCADONA SA with its registry sheet, V-5581.

Useful things to ask while you code

• "Check the SIRENs in fixtures/suppliers.json with Fuentio and flag any company that isn't active."
• "Look up one French and one Spanish company and write TypeScript types for the fields we use."
• "Verify DANONE (SIREN 552032534) and add its proof code to the test notes."
• "Why is this Spanish company's status unknown?" (the agent can call list_coverage and read the notes).

Good practice

• Keys stay out of repositories. Global file for Cursor, an input for VS Code.
• Ask for the source. Every answer carries its source and check date: have the agent quote them.
• Treat register text as data. Names and addresses come from the registers; your instructions decide what the agent does.
• Mind the units. A lookup costs 1 unit, a search 2 a page, a verification 5.

For Claude Code, see Fuentio in Claude Code, step by step; for the same data from your own code, the API quickstart. See what we cover.

Global or project configuration?

Both editors accept the server in two places. A global configuration follows you into every project: convenient for your own key. A project configuration lives in the repository: convenient to give the whole team the same tools, as long as it holds no key. A common setup is both: the project file declares Fuentio without a key (or with VS Code's input prompt), and each developer who has a key adds it in their global file or types it when asked.

Troubleshooting

Most problems come from the address, the key or the units. Each Fuentio error has a code, a message and a hint with the next step, and the agent sees them, so ask it to quote the error.

• The server doesn't connect. Check the address character by character: https://api.fuentio.com/mcp, over https. A company proxy or firewall can block outgoing connections from the editor or terminal; try from another network to rule it out.
• unauthorized. The key is unknown or revoked. Fix it, or remove the authorization header to fall back to the keyless trial while you sort it out.
• quota_exceeded. The units are used up. The keyless trial starts again the next day (UTC); a free key gives 100 units a month; paid plans give more. You are never charged for going over.
• rate_limited. The agent is calling too fast for your plan: the keyless trial allows about one request per second. Wait for the delay in the Retry-After header and ask the agent to slow down on long lists.
• A tool answers that it needs a key. Tools such as screen_company, review_report, watch_company, get_graph and report_issue need one. Add your key as shown above.
• id_scheme_not_supported for a Spanish company. The agent tried a NIF. Spanish companies are found by name: tell it to search by the registered name and province.

Limits. Editors change their settings screens often: if a menu name differs in your version, the JSON files above are the reference. The answers shown were recorded on 12 October 2026. France: every company in the public Sirene directory. Spain: companies with a BORME act since 2 January 2009, with a status that is unknown unless an act says otherwise. No person's name is ever returned.

Frequently asked questions

Do I need a key to use Fuentio in Cursor or VS Code?

No. Without a key, the server runs on the keyless trial, 20 units a day. A free key gives 100 units a month.

Where do I put my API key in Cursor?

In the headers of the Fuentio entry in your global ~/.cursor/mcp.json, not in a project file you commit.

How do I keep my key out of .vscode/mcp.json?

Declare a promptString input with password: true and reference it as ${input:fuentio-key} in the header. VS Code asks for the key once and keeps it outside the file.

How many tools does Fuentio add?

17, from list_coverage and lookup_company to verify_company, check_insolvency and watch_company. Some need a key.

Sources

• Fuentio setup for every client: connect and the docs
• The example answer: recorded from Fuentio's MCP server on 12 October 2026 (site/data/api-examples in the website repository)
• Cursor documentation, MCP: docs.cursor.com
• VS Code documentation, MCP servers: code.visualstudio.com