Fireworks AI MCP connector
The Fireworks AI connector lets Claude, ChatGPT, Cursor, or any MCP client work with your Fireworks AI accounts, batch inference jobs, datasets, clusters, and billing usage, with every request running as the signed-in person and recorded in an audit log.
-
How it connects. Connects with an API key. 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 Fireworks AI to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fireworks AI once
-
Open Connections, choose Add connection, and pick Fireworks AI.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Fireworks AI API key. One person generates a token in Fireworks AI and pastes it once. Everyone else works through Share with, and never sees it.
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.
Fireworks AI 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.
Fireworks AI 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.
Fireworks AI 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 Fireworks AI 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 Fireworks AI through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Machine learning
Start a batch inference job from chat
Ask for a batch inference job to be created against a dataset, then check on it later or cancel it if the run was a mistake, without opening the Fireworks AI console.
-
Data
Keep datasets organized for the next run
Create a new dataset, list what is already there, and confirm the right one is in place before anyone kicks off a job or a fine-tune.
-
Platform
Look after clusters without hunting through menus
List every cluster, create or update one, pull its connection details for a teammate, or remove one that is no longer needed.
-
Finance
Answer what Fireworks AI cost this month
Pull billing summaries and usage broken down by the available filters, so the monthly review takes a question instead of an export.
-
Security
Review who changed what in Fireworks AI
Read the account audit logs to see which person created a cluster, promoted a checkpoint, or deleted a job, and when.
-
Operations
Redeem credit codes and track the balance
Redeem a credit code the moment it arrives and list past redemptions so the team knows how much credit is left to spend.
Try asking
- “Summarize this month's Fireworks AI billing usage by account.”
- “List batch inference jobs that failed on the research account.”
- “Which Fireworks AI accounts burned the most credits last week?”
Compare
Elaichi vs Zapier MCP vs Composio for Fireworks AI
All three can connect Fireworks AI 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 Fireworks AI tools | Allow or restrict single Fireworks AI 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 Fireworks AI 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.
AI tools
Fireworks AI tools for your AI agents
206 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fireworks AI, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Fireworks AI gets you
6 screens from the product, each doing one job for your Fireworks AI account.
The agent
Ask in plain language, answer from live jobs.
Starter prompts pull batch inference jobs and billing usage straight from Fireworks AI.
- accounts
- batch inference jobs
- billing summaries
- audit logs
Ask Elaichi to work across your apps.
Summarize this month's Fireworks AI billing usage by account.
List batch inference jobs that failed on the research account.
Which Fireworks AI accounts burned the most credits last week?
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Reach Fireworks AI from any MCP client over OAuth, no SDK, no shared key.
Copy the endpoint
Tool catalog
206 Fireworks AI tools, no custom code.
Browse tool names, resources and methods covering accounts, inference jobs and billing summaries.
- List all Fireworks AI accounts
- Get single Fireworks AI account by ID
- Fireworks AI accounts test eval
- Create a Fireworks AI auth refresh
Toolboxes
Every team gets its own Fireworks AI toolbox.
Research, platform and finance each see a toolbox scoped to their own work.
- Research
- Platform
- Finance
- Security
Shared connections
Teammates use accounts they never hold keys to.
See who connected each Fireworks AI account and how many teams and members share it.
- Research
- Platform Prod
- Finance
- Sandbox
Audit log
Answer who ran which inference job, exactly.
Every call lands append only with when, who, what happened, type and resource.
- When
- Who
- What happened
- Type
Launching 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
A schedule fires, a digest gets approved.
Six steps fetch Fireworks AI jobs, group them, draft a digest, then post back.
Fireworks AI digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Fireworks AI
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
Fireworks AI
Queued
Collections and dashboards
Fireworks AI numbers computed, not asked for.
Four metrics, a 14 day chart of records created, and a per team breakdown.
Fireworks AI health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Batch inference jobs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Research 34%
Platform Prod 27%
Finance 21%
Sandbox 18%
FAQ
Frequently asked questions
How do I connect Fireworks AI to Claude?
Connect Fireworks AI in Elaichi first by pasting in a Fireworks AI API key from your account, which takes a minute. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi when prompted and Fireworks AI is ready to use.
Does Fireworks AI work with ChatGPT and Cursor as well as Claude?
Yes. Once Fireworks AI is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Fireworks AI once and every client you use picks it up.
What can an AI agent actually do with my Fireworks AI data?
Through Elaichi, an agent can list your Fireworks AI accounts, create and check batch inference jobs, create and list datasets, manage clusters, promote checkpoints, redeem credit codes, and read billing summaries, usage, and audit logs. Because Fireworks AI exposes a large set of actions, the agent searches for the right one as you ask, so a short concrete request such as "list this month's billing usage" works better than a long paragraph.
Does connecting Fireworks AI give the AI access to everything in my account?
No. Access to Fireworks AI follows the person who signed in, so the agent can only reach the accounts, jobs, clusters, and billing details that person's Fireworks AI key already allows. Elaichi can narrow that further by turning off individual actions, and it can never widen it beyond what Fireworks AI itself permits.
Can I stop an agent from deleting or changing things in Fireworks AI?
Yes. In Elaichi you can restrict Fireworks AI action by action, for example allowing the agent to read billing usage and list jobs while blocking the ability to delete batch inference jobs or remove clusters. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to a Fireworks AI connection when someone leaves?
When you offboard someone in Elaichi, their access to Fireworks AI through every client ends at once. A Fireworks AI connection that was shared with a team keeps working for everyone else on it. If you ever want to remove Fireworks AI entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other connected client.
Does the Fireworks AI MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fireworks AI 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 Fireworks AI?
Yes. Both let Claude, ChatGPT or Cursor use Fireworks AI. 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 Fireworks AI call.
How is Elaichi different from Composio for Fireworks AI?
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 Fireworks AI: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fireworks AI 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.