How to connect GLEIF API to Claude

Connect Claude Web, Desktop and Cowork to GLEIF API MCP. Lookup lei details for 5493001kjtiigc8y1r12, list ultimate parents for lei 213800k2r6r5mvyq4d30, and more using natural language, with authentication handled for you.

GLEIF API logoGLEIF API
No Auth

GLEIF provides free public access to Legal Entity Identifier records and related reference data. Access standardized LEI data, ownership relationships, and identifier mappings.

20 Tools

Introduction

Claude is Anthropic's AI assistant, available on the web, in the desktop app, and on mobile. Cowork is its agent for knowledge work, and it runs on all of those surfaces too. Connected to your apps, Claude can work with your files and services to accomplish complex tasks on your behalf.

This guide walks you through the easiest and most secure way to connect your GLEIF API account to Claude via Composio Connect, enabling it to lookup LEI details for 5493001KJTIIGC8Y1R12, list ultimate parents for LEI 213800K2R6R5MVYQ4D30, map external identifiers to LEI for company, and more such actions on your behalf without compromising your account security.

Setup is the same on Claude Web, Desktop, and Cowork, and you only need to do it once. The connector is tied to your account, so it's available in all three.

Also integrate GLEIF API with

Connecting GLEIF API to Claude Web, Desktop, and Cowork

1. Open Customize

In Claude Desktop, click Customize in the left sidebar, then select Connectors and click the + icon at the top.

Claude Desktop connectors screen with Add custom connector selected

2. Add the Composio MCP server

Click Add custom connector and paste in the Composio MCP server URL:

bash
https://connect.composio.dev/mcp
Add custom connector dialog with Composio MCP server URL

3. Authorize in your browser

Click Connect. You'll be redirected to a browser window where you can authorize Composio to continue.

Composio authorization screen for Claude Web, Desktop, and Cowork

4. Connect your GLEIF API account

Back in Claude, ask it to connect to GLEIF API or give it any GLEIF API-related task.

For example, ask Claude to:

  • "Lookup LEI details for 5493001KJTIIGC8Y1R12"
  • "List ultimate parents for LEI 213800K2R6R5MVYQ4D30"
  • "Map external identifiers to LEI for company"

It will prompt you to authenticate and authorize access.

That's it. Composio's tools are now available in Claude, and your GLEIF API account is ready to use.

What is the GLEIF API Claude Connector, and what's possible with it?

The GLEIF API MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your GLEIF API account. It provides structured and secure access so your agent can perform GLEIF API operations on your behalf.

Troubleshooting

1. Why does Claude not use the Composio connector for GLEIF API?

The connector can show as connected, but Claude must use it in each GLEIF API conversation.

  • Click + at the lower left of the chat, or type /.
  • Hover Connectors.
  • Turn on Composio.
  • Ask Claude to connect to GLEIF API again.

2. Why does Claude show an MCP server error before GLEIF API connects?

Claude can show Couldn't reach the MCP server or Authorization with the MCP server failed when you add the connector for GLEIF API.

  • Check that the connector URL is https://connect.composio.dev/mcp.
  • Connectors run from Anthropic's cloud, so your device network is usually not the problem.
  • Add the connector again from Customize > Connectors, then ask Claude to connect GLEIF API.
  • If it fails again, send the error and the ofid_ reference id to support@composio.dev.

3. Why does the GLEIF API authorization link not work?

The Composio connector is one server. Your GLEIF API account connects separately when Claude asks for it.

  • If the browser does not open, or the link expires, ask Claude to retry the GLEIF API connection.
  • Composio creates a fresh GLEIF API authorization link.
  • Open that link in your browser and finish the GLEIF API sign-in.

4. Why do GLEIF API actions fail after they worked before?

The GLEIF API connection can expire or lose permission.

  • Ask Claude to inspect the GLEIF API connection.
  • If the connection is unhealthy, disconnect it when Claude prompts you.
  • Reconnect the GLEIF API account and retry the action.
  • If Claude shows a permission prompt, approve it before Claude changes data in GLEIF API.
  • If the action still fails with a permission error, check that the connected account has that permission in GLEIF API itself.

5. How do I switch to a different GLEIF API account?

Claude can manage the GLEIF API connection for you.

  • Ask Claude to disconnect or delete the current GLEIF API account.
  • Ask Claude to connect GLEIF API again.
  • Open the new Composio authorization link for GLEIF API.
  • Sign in with the other GLEIF API account in the browser.
  • After the account connects, ask Claude to retry the GLEIF API task.

6. Why is my GLEIF API connection missing in Claude Desktop or on a Team plan?

The connector belongs to your Claude account, so your GLEIF API connection works in Claude Web, Desktop, and Cowork.

  • In Claude Desktop, open Customize > Connectors.
  • Next to Composio, click and click Clear cache.
  • If GLEIF API tools still do not appear, click , disconnect, remove the connector, and add it again.
  • On Team or Enterprise, an Owner or Primary Owner must enable the connector before you can connect GLEIF API.
TOOLS

Supported Tools

Every GLEIF API action and event your agent gets out of the box.

Export LEI Records

Download up to 5,000 LEI records using the complete closed field-filter and sort surface as CSV, XLSX, JSON, or XML.

Get Autocompletions

Return prefix-based GLEIF search suggestions from the provider's data collection, defaulting absent top-level metadata and links to empty objects.

Get Fund or Branch Relationship

Get the complete relationship record linking an LEI to its fund manager, umbrella fund, master fund, or head office.

Get Fuzzy Completions

Find approximate GLEIF search matches for misspelled or incomplete input.

Get LEI Issuer for Record

Get the complete LEI-issuer reference resource associated with a specified LEI record.

Get LEI Record

Retrieve one LEI record with complete provider attributes, relationships, links, and Golden Copy metadata when its LEI is known.

Get Parent Information

Get a direct or ultimate parent LEI plus complete relationship evidence, or the complete reporting exception when no parent is reported.

Get Reference Item

Get one complete item from a selected GLEIF reference collection by its collection-specific identifier.

Get Related LEI Record

Follow a selected associated-entity, managing-LOU, fund, or head-office link and return the complete related LEI record.

List Child Entities

List one page of complete direct or ultimate accounting-child LEI records.

List Child Relationships

List one page of complete direct or ultimate accounting-child relationship records for an LEI.

List Fund or Branch Entities

List one page of complete managed-fund, sub-fund, feeder-fund, or international-branch LEI records.

List Fund or Branch Relationships

List one page of complete fund-management, sub-fund, feeder-fund, or international-branch relationship records.

List LEI Field Modifications

List one page of complete LEI, relationship, or reporting-exception field-history resources with optional type, XPath, and date filters.

List LEI ISINs

Return one page of complete GLEIF-ANNA ISIN mappings for an issuer LEI.

List LEI Issuer Jurisdictions

List one page of complete jurisdiction resources for which an LEI issuer is accredited.

List Reference Data

List one complete JSON:API page from a selected GLEIF field, code, or issuer reference collection.

List Registration Agents

List all GLEIF registration agents, optionally filtered by issuer LEI or registration-agent LEI.

List Successor Entities

List one page of all successor LEI records for an entity.

Search LEI Records

Search LEI records with closed, field-aware filters and sorting, returning one complete JSON:API page.

FRAMEWORKS

How to build GLEIF API MCP Agent with another framework

FAQ

Frequently asked questions

With a standalone GLEIF API MCP server, the agents and LLMs can only access a fixed set of GLEIF API tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from GLEIF API and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Claude Cowork fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right GLEIF API tools.

Yes, absolutely. You can configure which GLEIF API scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your GLEIF API data and credentials are handled as safely as possible.

Start with GLEIF API.It takes 30 seconds.

Managed auth, hosted MCP servers, and every GLEIF API tool your agent needs.Free to start.

Start building