# Pydantic Logfire (EU) MCP connector

Connecting Pydantic Logfire (EU) to Elaichi lets Claude, ChatGPT, Cursor and the Elaichi Agent query your telemetry with SQL, surface recent exceptions, and manage dashboards, alerts and issues, all inside each person's own access.

Source: https://elaichi.ai/connectors/logfire-eu/

## Facts

| | |
| --- | --- |
| Application | Pydantic Logfire (EU) |
| Category | Observability |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Pydantic Logfire (EU) builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | pydantic.dev/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Pydantic Logfire (EU) is connected

- Show exceptions in the checkout service from the last hour
- Which alerts fired overnight and are any still open?
- Add a p95 latency panel to the API dashboard

## Connect Pydantic Logfire (EU) in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Pydantic Logfire (EU).
2. Optionally set Share with, then press Connect.
3. Approve it in Pydantic Logfire (EU). Pydantic Logfire (EU)'s own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Pydantic Logfire (EU) tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Pydantic Logfire (EU) MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Pydantic Logfire (EU) MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Pydantic Logfire (EU) MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Pydantic Logfire (EU) to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Pydantic Logfire (EU) tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Pydantic Logfire (EU) through Elaichi

### Find out why last night's deploy got noisy

Engineering. Ask which exceptions started appearing after the release and get the matching traces with their error messages, without writing the SQL yourself.

### Triage an alert before paging anyone else

On-call. When an alert fires, ask what it is watching, which service tripped it, and whether the same issue was already open last week.

### Check a customer's failed request

Support. Give the agent a request ID or a customer email and get back the trace, the error and the time it happened, in plain language.

### Keep dashboards in step with new services

Platform. Ask the agent to add a panel for a newly deployed service or copy a dashboard layout for a second environment.

### Get a weekly read on endpoint usage

Product. Ask how often a new endpoint was hit this week and how that compares to last week, pulled straight from telemetry.

### Close out issues that stopped reproducing

QA. Ask which open issues have not recurred in seven days and close them with a note, so the issue list stays honest.

## Elaichi vs Zapier MCP vs Composio for Pydantic Logfire (EU)

All three can connect Pydantic Logfire (EU) to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Pydantic Logfire (EU) tools | Allow or restrict single Pydantic Logfire (EU) tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Pydantic Logfire (EU) call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Pydantic Logfire (EU) to Claude?

Two steps. In Elaichi, pick Pydantic Logfire (EU) and connect it over OAuth: you sign in to your EU Logfire account and approve access, with no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude now reaches Pydantic Logfire in EU as you.

### Does Pydantic Logfire (EU) work with ChatGPT and Cursor as well as Claude?

Yes. Pydantic Logfire (EU) is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing extra to set up per client.

### What can an AI agent actually do with my Pydantic Logfire (EU) data?

It can run SQL against your Pydantic Logfire (EU) telemetry, pull up recent exceptions with their traces, and create or update dashboards, alerts and issues. In practice you ask things like which errors appeared after the last deploy or whether an alert is still firing. Short, concrete asks work better than long sentences.

### Does connecting Pydantic Logfire (EU) give the AI everything in my project?

No. Every call to Pydantic Logfire in EU runs as the person who signed in, so the agent sees only the projects and telemetry that person can already see. Elaichi can narrow that further with roles and restrictions, and it can never widen it.

### Can my team share one Pydantic Logfire (EU) connection?

Yes. One person connects Pydantic Logfire (EU) in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every query to Logfire in EU.

### Can I stop an agent from deleting or changing things in Pydantic Logfire (EU)?

Yes. Restrictions in Elaichi work per action, so you can allow reading telemetry and exceptions from Pydantic Logfire (EU) while blocking changes to dashboards, alerts or issues. A restricted action is never advertised to the AI client at all, so no prompt can reach it.

### What happens to a Pydantic Logfire (EU) connection when someone leaves?

Offboarding that person in Elaichi ends their access to Pydantic Logfire (EU) at once, across every client they used. A connection they shared keeps working for everyone else on the team. If you want it gone entirely, disconnecting Pydantic Logfire in EU once in Elaichi removes it from every client.

### Does the Pydantic Logfire (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Pydantic Logfire (EU) is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Pydantic Logfire (EU)?

Yes. Both let Claude, ChatGPT or Cursor use Pydantic Logfire (EU). Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Pydantic Logfire (EU) call.

### How is Elaichi different from Composio for Pydantic Logfire (EU)?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Pydantic Logfire (EU): one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.