Connect an MCP client to FinData
Connect an MCP client using Streamable HTTP and a FinData API bearer token.
What you need
FinData exposes a read-only Streamable HTTP MCP endpoint at https://mcp.findata.com/mcp. You need an MCP client that supports a remote Streamable HTTP server and a custom Authorization header, plus an API credential accepted by api.findata.com.
Get a short-lived OAuth access token at https://api.findata.com/access, or use an existing operator key if one has been supplied to you. The MCP server forwards the bearer credential to the API; it does not implement its own login or OAuth discovery. The help-centre account session is not an API token.
Connect
- Create or configure a remote MCP server in your client.
- Set the transport to Streamable HTTP and the URL to https://mcp.findata.com/mcp.
- Configure an Authorization header with the value Bearer followed by your API token.
- Connect, list tools, and try a company search. Client configuration screens vary; use your client’s documentation for exact syntax.
Store credentials securely. Do not paste tokens into prompts, screenshots, public configuration files or issue reports. The self-service token expires; return to https://api.findata.com/access to obtain a fresh token and update the header in your client.
A first question
Ask your client: “Find Apple in FinData and show the most recent available reported annual revenue, with the filing source.” The client can use search_companies, get_company and get_metrics. Review the returned period, unit, source and limitations before drawing a conclusion.
Troubleshooting
A missing bearer header receives 401. The server checks the header’s shape during initialization; an invalid but syntactically valid token can list tools yet fail when a tool calls the API. If a tool returns 401, check token validity, expiration and API audience. A 429 is an API rate limit; wait and retry. The MCP server is read-only and does not bypass API coverage or limits.