Community-built server
Does Fidelity have an MCP server?
No public first-party MCP documentation from Fidelity was found in this review. Two unofficial third-party servers exist: one from Strider Labs covering brokerage, IRA and 401(k) account viewing, and a community browser-automation project.
The community project describes relying on browser automation rather than a documented Fidelity retail account-data API, per its own repository notes at https://github.com/TylerFlar/claude-fidelity-mcp. Browser automation against a brokerage login carries real account-security and terms-of-service risk; review Fidelity's terms before using it.
The Strider Labs server, distributed via npm at https://www.npmjs.com/package/@striderlabs/mcp-fidelity, is third-party software that Fidelity did not write, review or support, and nothing commits the author to tracking changes on Fidelity's side. Start read-only, and audit what OAuth grant, if any, it requests.
Advisor-side Fidelity access, such as Wealthscape Institutional Wealth Services, is a separate system from retail Fidelity.com login; neither listed server documents institutional Wealthscape coverage, and Truthifi's own material distinguishes Wealthscape Investor from retail Fidelity, see https://truthifi.com/connect-hubs/ai-investor-portals. Confirm which Fidelity surface, retail or institutional, a given connection actually reaches.
These third-party implementations are not institutional custody integrations by default. Start with read-only scopes where offered and review credential handling before connecting. A directory listing is not an endorsement.
What works today
Fidelity MCP Server (Strider Labs)
VendorFidelity MCP Server, Strider Labs
Auth: OAuthLocalFidelity MCP Server (claude-fidelity)
CommunityFidelity MCP Server, community browser automation
Auth: NoneLocal
Last checked: 2026-10-13
Work at Fidelity, or know of a server we have missed? Tell us.
All vendor answers →