How do I give an n8n AI Agent access to fund data?
Attach an HTTP Request Tool or the MCP Client node to an n8n AI Agent so it can look up any ISIN and answer with current TER, holdings, exposures and returns. No code.Published September 12, 2026 · Updated October 13, 2026 · by FundFacts APIShort answer
Add an HTTP Request Tool to the AI Agent node with URL https://fundfactsapi.com/api/v1/funds/{isin} (let the model fill the ISIN), a Header Auth credential carrying Authorization: Bearer <key>, a 300000 ms timeout and the description "current factsheet of a fund or ETF by ISIN". Or add the MCP Client Tool node pointing at https://fundfactsapi.com/api/mcp with the same header to get all seven tools at once. The agent then answers fund questions with published figures.
HTTP Request Tool
- Add an AI Agent node with your chat model.
- Under Tools, add HTTP Request Tool:
- Description: Current factsheet of a fund or ETF by 12-character ISIN: name, TER, risk 1-7, holdings, sector and country split, returns, as-of date. - Method GET, URL https://fundfactsapi.com/api/v1/funds/{isin} with the isin placeholder set to "let the model define". - Authentication: Generic → Header Auth, name Authorization, value Bearer ffk_.... - Options → Timeout 300000 (a cold ISIN can take minutes on first load).
- Optionally add a second tool for
https://fundfactsapi.com/api/v1/search?q={query}(free) so the agent can resolve names to ISINs.
Keep the system message short: "Use the tools for any fund question. Quote dataAsOf with figures. Empty fields mean not disclosed."
MCP Client Tool
The MCP Client Tool node connects the agent to a remote server:
| Setting | Value |
|---|---|
| Endpoint | https://fundfactsapi.com/api/mcp |
| Transport | HTTP Streamable |
| Authentication | Header Auth, Authorization: Bearer ffk_... |
The MCP server exposes seven tools, each counted like the REST endpoint it wraps: get_fund (ISIN → the full factsheet payload), search_funds (name → ISINs, free), compare_funds (side-by-side table for several ISINs), analyze_portfolio (weighted look-through of a list of positions, Starter and above), fund_overlap (shared holdings between funds, Starter and above), get_scpi (French SCPI data by name or ISIN) and search_scpi (SCPI name → matches, free), plus a tour prompt that explains the service on the example fund IE00B4L5Y983, which is not counted. Every tool only reads data. Authentication is either your FundFacts account (OAuth 2.1 with PKCE, the sign-in the claude.ai, Claude Desktop and ChatGPT connectors run) or the same bearer API key as the REST API, sent as an Authorization header by editors, CLIs and frameworks. The MCP server guide has the full tool reference, setup for every client and troubleshooting.
Cost
One request per fund found, exactly like calling the REST endpoint from an ordinary HTTP Request node. The n8n lookup page shows the non-agent version with a ready-to-paste workflow.
Verify it yourself
The demo endpoint returns the live payload for a fund that is already in the store, without a key. Everything on this page can be checked against it.bashcurl -s https://fundfactsapi.com/api/v1/demo/funds/IE00B4L5Y983 | jq '{name, asOf: .data.dataAsOf, ter: .data.headlineMetrics.ter, risk: .data.riskRating, top: .data.topHoldings[:3]}'