Atomicwork MCP connector
The Atomicwork connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, or any MCP client raise, find, and update Atomicwork requests, assets, and changes, with every action running as the signed-in person and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
ChatGPT
Elaichi connected
Show open Atomicwork requests by workspace this week.
Working in Atomicwork with Elaichi
-
List all Atomicwork service catalog categories
-
-
Governance
/
Audit log
Last 24 hours
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
ChatGPT · 9:41 AM
Done
Claude · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect Atomicwork to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Atomicwork 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.
Atomicwork MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Atomicwork 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. The plugin directory lives at chatgpt.com/plugins.
Atomicwork 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.
Atomicwork MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Atomicwork 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.
What teams do with Atomicwork through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Atomicwork is logged.
-
IT service desk
Raise a request while still on the call
Describe the problem a colleague just reported and a new Atomicwork request is created with the right priority, so nothing is lost between the conversation and the queue.
-
IT service desk
Catch a request up after the fix
Once the laptop is working again, dictate what was done and it lands as an activity note on the Atomicwork request, then the request is updated or closed.
-
IT operations
See what is open and how urgent
Ask how many Atomicwork requests are waiting by priority or in a saved view, and get a plain answer from live records before the Monday stand-up.
-
Asset management
Log new hardware the day it arrives
Read out the model and serial number from the delivery and a new asset is recorded in Atomicwork, ready to be assigned to a person or a workspace.
-
Change management
Draft a change record before the maintenance window
Turn the notes from a planning meeting into an Atomicwork change with the scope, timing, and reason already filled in, so approvers see it in time.
-
Security and compliance
Answer who did what in Atomicwork
Pull Atomicwork audit logs and workspace member lists for a review, and check that the people with access are the people who should have it.
Try asking
- “Show open Atomicwork requests by workspace this week.”
- “Create an Atomicwork request for a replacement laptop.”
- “List Atomicwork assets assigned to the support team.”
What connecting Atomicwork gets you
6 screens from Elaichi, each doing one job for your Atomicwork account.
Ask Elaichi to work across your apps.
Show open Atomicwork requests by workspace this week.
Create an Atomicwork request for a replacement laptop.
List Atomicwork assets assigned to the support team.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about requests, get real answers.
Type a question in plain language and read live Atomicwork requests and assets.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One endpoint reaches Atomicwork from anywhere.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK, no shared API key.
ElaichiToolsTool catalog
37 Atomicwork tools ready on connect.
Requests, assets, changes and workspace members are covered without custom code.
ElaichiToolboxesToolboxes
Every team gets its own toolbox.
Curate Atomicwork toolboxes per team so IT, HR and support see their scope.
ElaichiConnectionsShared connections
Teammates use Atomicwork without a credential.
See who connected each account and how many teams and members share it.
ElaichiAudit logAudit log
Answer who touched which request.
Append-only rows record when, who, what happened, type and resource in Atomicwork.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Atomicwork digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch requests
Atomicwork
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 Jake Morgan
Approve Deny -
Post the digest
Atomicwork
Queued
Automations
A schedule works your Atomicwork queue.
Fetch requests, group them, draft a digest, approve it, post it back.
Atomicwork health
Refreshed 4 minutes ago · every 15 minutes · from the requests collection
Requests
1,284 ↓ 12%
Assets
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Requests created
Last 14 days
By team
Share of activity
IT service desk 34%
HR operations 27%
Facilities 21%
Change board 18%
Collections and dashboards
Atomicwork request health, computed on schedule.
Four metrics, 14 days of requests created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Atomicwork
All three can connect Atomicwork 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 Atomicwork tools | Allow or restrict single Atomicwork 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 Atomicwork 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 | Free for one person; $15 per user per month on Gold. | 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.
Atomicwork tools for your AI agents
37 tools are ready to call through Elaichi's MCP endpoint the moment you connect Atomicwork, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Atomicwork to Claude?
Connect Atomicwork in Elaichi by pasting an API key from your Atomicwork account, which takes about a minute, and there is no client ID or secret to generate and no OAuth application to register. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on Atomicwork is available in your conversations.
Does Atomicwork work with ChatGPT and Cursor as well as Claude?
Yes. Once Atomicwork is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Atomicwork once and every client you use picks it up.
What can an AI agent actually do with my Atomicwork data?
An agent can create Atomicwork requests and changes, find a request by its number or search across them, count what is open by priority or view, add activity notes, update or delete a request, and record new assets. It can also browse the service catalog, list requesters and workspace members, read audit logs, and create assessment forms. Because Atomicwork has a lot of actions available, short concrete asks such as "count open requests with high priority" work better than long paragraphs.
Does connecting Atomicwork give the AI access to every workspace and request?
No. The AI only reaches what the signed-in person can already reach in Atomicwork, so the workspaces, requests, and assets available to them are the ones available to the agent. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Atomicwork itself allows that person.
Can I stop an agent from deleting or changing things in Atomicwork?
Yes. Restrictions in Elaichi apply per action, so you can allow creating and searching Atomicwork requests while restricting deleting them or editing workspace members. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to an Atomicwork connection when someone leaves?
Offboarding a person in Elaichi ends their access to Atomicwork through every client at once. If they connected a shared Atomicwork account, that connection keeps working for everyone else on the team. Disconnecting Atomicwork once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Atomicwork MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Atomicwork 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, Microsoft Copilot, 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 Atomicwork?
Yes. Both let Claude, ChatGPT or Cursor use Atomicwork. 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 Atomicwork call.
How is Elaichi different from Composio for Atomicwork?
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 Atomicwork: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Atomicwork in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
- ChatGPT
- Claude
- Cursor
- Microsoft Copilot