How do AI agents use OpenFIGI through Open Connector?

Your user connects OpenFIGI once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes OpenFIGI tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a OpenFIGI MCP server?

Yes. Open Connector can serve OpenFIGI as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call OpenFIGI actions with credentials injected server-side.

Where do OpenFIGI credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

OpenFIGI integration

OpenFIGI integration for AI agents.

OpenFIGI integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves OpenFIGI tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real OpenFIGI actions, managed and audited.

Your user connects OpenFIGI once; your agent can then discover and map financial instrument identifiers using the OpenFIGI API — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants OpenFIGI access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported OpenFIGI tools.

4 tools are generated from the published OpenFIGI catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 4 tools. All published catalog entries are included in this page's server-rendered HTML.

Get Mapping Values Key: Get values for enum-like fields.; mapping
Post Filter: Search for FIGIs using key words and other filters. The results are listed alphabetically by FIGI and include the number of results.; post
Post Mapping: Allows mapping from third-party identifiers to FIGIs.; post
Post Search: Search for FIGIs using key words and other filters.; post

FAQ

OpenFIGI integration, answered

How do AI agents use OpenFIGI through Open Connector?: Your user connects OpenFIGI once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes OpenFIGI tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a OpenFIGI MCP server?: Yes. Open Connector can serve OpenFIGI as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call OpenFIGI actions with credentials injected server-side.
Where do OpenFIGI credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents OpenFIGI — keep the keys.

Open source, self-hostable, with OpenFIGI credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →