Pydantic Logfire MCP connector
Connect Pydantic Logfire to Elaichi and Claude, ChatGPT, Cursor and the Elaichi Agent can query your traces with SQL, surface recent exceptions and manage dashboards, alerts and issues, each person signed in as themselves.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Pydantic Logfire to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pydantic Logfire once
-
Open Connections, choose Add connection, and pick Pydantic Logfire.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Pydantic Logfire. Pydantic Logfire's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Pydantic Logfire MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Pydantic Logfire MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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 MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Pydantic Logfire to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Pydantic Logfire through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Engineering
Find out what broke after a deploy
Ask which services started throwing exceptions in the last hour and get the stack traces back in the chat. Then open an issue in Pydantic Logfire for the one that matters without leaving the conversation.
-
On-call
Triage alerts before the standup
Ask which alerts fired overnight, which are still open and what each one points at. Close the noisy ones and leave a note on the rest so the next person knows where things stand.
-
Platform
Build a dashboard from a plain question
Describe the dashboard you want, say p95 latency per endpoint for the payments service, and have it created in Pydantic Logfire. Adjust the panels by asking rather than by clicking through settings.
-
Support
Check a customer's error before replying
Paste a customer's request ID and ask what happened to that trace. The agent pulls the spans and exceptions so the reply to the customer is accurate the first time.
-
Product
Measure how a feature is behaving
Ask how often a new endpoint was called this week and how slow the worst requests were. The answer comes from a SQL query over your spans, not from a guess.
-
Data
Run SQL over telemetry without the console
Ask for error counts by service and day, or the slowest queries this month, and have the SQL written and run against Pydantic Logfire for you. Refine the question and run it again.
Try asking
- “Show me the exceptions from the last hour in the checkout service.”
- “Which alerts fired overnight and are any still open?”
- “Create a dashboard tracking p95 latency for the payments API.”
Compare
Elaichi vs Zapier MCP vs Composio for Pydantic Logfire
All three can connect Pydantic Logfire 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.
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 tools | Allow or restrict single Pydantic Logfire 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 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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
See it in Elaichi
What connecting Pydantic Logfire gets you
5 screens from the product, each doing one job for your Pydantic Logfire account.
The agent
Ask what broke overnight and get live answers.
The Elaichi Agent queries your Pydantic Logfire spans and exceptions as they are right now.
- spans
- exceptions
- dashboards
- alerts
Ask Elaichi to work across your apps.
Show me the exceptions from the last hour in the checkout service.
Which alerts fired overnight and are any still open?
Create a dashboard tracking p95 latency for the payments API.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One governed endpoint, every client, no shared key.
Claude, ChatGPT and Cursor reach Pydantic Logfire through one org endpoint, each person signed in.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Pydantic Logfire toolbox.
On-call sees alerts and issues, Data sees SQL queries, scoped by team in Elaichi.
- Engineering
- On-call
- Platform
- Support
ElaichiToolboxesShared connections
Share one Pydantic Logfire connection, never a credential.
Teammates query spans and manage alerts through a shared connection without seeing a token.
- Backend
- Platform
- On-call
- Support
ElaichiConnectionsAudit log
Every query and alert change is written down.
Who ran which SQL, who closed which issue, when, all in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
Overnight exceptions become a reviewed digest by morning.
Pydantic Logfire exceptions are fetched, grouped, drafted and approved before an issue is filed.
Pydantic Logfire digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch spans
Pydantic Logfire
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Pydantic Logfire
Queued
Collections and dashboards
Exception and alert counts, refreshed without asking.
Four metrics, a 14 day chart and a team breakdown, computed with no model involved.
Pydantic Logfire health
Refreshed 4 minutes ago · every 15 minutes · from the spans collection
Spans
1,284 ↓ 12%
Exceptions
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Spans created
Last 14 days
By team
Share of activity
Backend 34%
Platform 27%
On-call 21%
Support 18%
FAQ
Frequently asked questions
How do I connect Pydantic Logfire to Claude?
Connect Pydantic Logfire in Elaichi first, which means signing in to Pydantic Logfire over OAuth in your browser, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Claude signs you in to Elaichi and your Pydantic Logfire tools are available in the next chat.
Does Pydantic Logfire work with ChatGPT and Cursor as well as Claude?
Yes. Pydantic Logfire is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor or any other MCP client. The Elaichi Agent uses it as well, so there is nothing separate to set up per client.
What can an AI agent actually do with my Pydantic Logfire data?
It can run SQL against your Pydantic Logfire spans and traces, pull up recent exceptions with their stack traces, and create or change dashboards, alerts and issues. In practice that means asking what broke in the last hour, which alerts are still open, or how slow an endpoint was this week. Short concrete asks work better than long paragraphs, so name the service or the time window you care about.
Does connecting Pydantic Logfire give the AI access to every project?
No. Every call to Pydantic Logfire runs as the person who signed in, so the agent sees the projects and organizations that person can already open and nothing more. Elaichi can narrow that further with restrictions per action, and it can never widen it beyond what Pydantic Logfire itself allows.
Can I stop an agent from deleting or changing things in Pydantic Logfire?
Yes. Restrictions in Elaichi work per action, so you can allow reading spans and exceptions while blocking changes to dashboards, alerts or issues in Pydantic Logfire. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.
What happens to a Pydantic Logfire connection when someone leaves?
Offboarding that person in Elaichi ends their access to Pydantic Logfire through every client at once. A shared Pydantic Logfire connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the Pydantic Logfire MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pydantic Logfire 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?
Yes. Both let Claude, ChatGPT or Cursor use Pydantic Logfire. 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 call.
How is Elaichi different from Composio for Pydantic Logfire?
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: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Pydantic Logfire in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.