The FMP MCP server for Claude is an official remote tool connection
FMP’s official MCP page publishes a remote server URL and lists Claude as a compatible client. The server exposes traditional FMP API capabilities as MCP tools with names, descriptions and required parameters. Claude can discover those tools and request a call when a question needs company, statement, market or related financial data.
Every call still consumes FMP access under the key’s plan and limits. MCP does not make unavailable endpoints available, guarantee factual answers, grant redistribution rights, or remove the need to verify dates, units and source records.
How to connect the FMP MCP server for Claude
The official FMP guide uses a remote URL containing the API key as a query parameter. Treat the complete URL as a secret. Interface labels and connector availability can vary by Claude product, plan, organization policy and release, so use the current Claude settings screen rather than relying on an old screenshot.
Create or choose a dedicated FMP key
Avoid reusing a broadly shared production key. Record its owner, purpose, plan, permitted environment and rotation date.
Build the official remote URL
Use FMP’s documented MCP endpoint and replace the placeholder with the key. Do not paste the completed URL into tickets, chat messages, screenshots or source control.
Add a custom connector in Claude
Open the available connector settings, create a custom remote connection, give it an unambiguous name and paste the URL only into the intended server field.
Start a new conversation and inspect tools
Confirm that FMP tools are visible before asking for data. Tool names and catalog size may change, so inspect the actual list rather than assuming every REST endpoint is present.
Run a minimal read-only test
Request one known symbol and one narrow dataset, then review the proposed tool, parameters, result date, units and source before expanding scope.
Document and monitor the connection
Store the connector owner, approved use cases, expected tools, quota budget, incident contact and revocation procedure—never the secret URL itself.
https://financialmodelingprep.com/mcp?apikey=YOUR_FMP_API_KEYThe placeholder is safe to document; a completed URL is a credential. This page intentionally does not show a real key.
Primary sources: FMP official MCP server guide and Anthropic MCP documentation. Recheck both products before deployment.
Verify the connection before trusting the answer
Discovery
Visible server name, tool list and tool schemas.
No tools, unexpected server, duplicate connector.
Authentication
Successful narrow request and account usage record.
Unauthorized response, invalid key or plan denial.
Semantics
Symbol, period, units, currency, timestamp and raw fields.
Wrong period, stale date, unit ambiguity or missing fields.
Limits
Requests consumed, 429 behavior, retry message and quota owner.
Unbounded retries, silent partial result or surprise spend.
Provenance
Tool name, arguments, provider, retrieval time and record date.
Answer cannot be traced to a tool result.
Treat financial MCP access as a credentialed production integration
Protect the complete URL
A query-string key may appear in browser history, screenshots, proxy logs, diagnostics or copied configuration. Limit who can view the connector, prefer a dedicated key, monitor usage and rotate after suspected exposure.
Constrain calls and prompts
Use explicit symbols, dates, periods and maximum result sizes. Treat retrieved news, filings and text as untrusted content: they may contain instructions that should never override system or business policy.
Respect plan and license boundaries
Tool availability does not prove permission to display, store, derive or redistribute data. Match the workflow to the current FMP account, agreement and user audience.
Separate data from interpretation
Preserve the provider result, then label calculations and model interpretation separately. Require review for investment, compliance, customer-facing or other consequential use.
Diagnose FMP MCP problems by layer
The server does not appear
Check Claude product support, organization policy, connector state, the exact remote URL and whether a new conversation is required after configuration.
Tools appear but calls fail
Check key validity, plan access, endpoint entitlement and account status. Rotate rather than repeatedly sharing the secret URL during support.
Calls are throttled or incomplete
Reduce scope, bound date ranges, cache approved results, add backoff and surface partial-result status. Never let an agent retry without a budget.
The answer looks plausible but wrong
Inspect the actual tool arguments and result. Recheck fiscal period, currency, units, adjusted versus unadjusted values, filing date, revision and whether Claude combined multiple records.
Use QVeris to add policy and provenance around FMP tools
A governed discovery layer
QVeris can help expose authorized financial tools to AI workflows with user, environment and task boundaries. A policy can require symbols and dates, cap result sizes, separate test and production credentials, and record which tool produced each dataset.
What governance cannot replace
QVeris does not create FMP entitlements, guarantee data or model accuracy, provide investment advice, or grant storage and redistribution rights. Those remain provider, contract, application and human-review responsibilities.
Related guides: financial RAG architecture, LLMs for financial analysis, and FMP vs Polygon.io.
FMP MCP server for Claude questions
Does FMP have an official MCP server for Claude?
Yes. FMP publishes an official remote MCP URL and lists Claude as a compatible client. Use the FMP documentation rather than confusing it with unrelated community servers.
How do I connect FMP MCP to Claude?
Add a custom connector in the supported Claude settings using FMP’s official URL with an active key. Start a new chat, inspect discovered tools and run a narrow read-only test.
Do I need to install a local MCP server?
Not for the official remote path documented by FMP. Local or self-hosted community implementations are separate choices with different code, trust, update and operational responsibilities.
Is it safe to put an FMP API key in the MCP URL?
The completed URL is a credential and may leak through history, logs, screenshots or sharing. Use a dedicated key where possible, restrict visibility, monitor usage and rotate or revoke after exposure.
Why are some FMP tools unavailable in Claude?
Availability can depend on the current MCP catalog, FMP plan, endpoint entitlement, key state, Claude client support, organization policy and service status.
Can QVeris govern an FMP MCP workflow?
QVeris can add authorized discovery, parameter policy, quota controls, provenance and review gates. It does not grant FMP data rights or guarantee the resulting financial analysis.