Can my team share one Atomicwork connection?

Yes. One person connects Atomicwork in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so every request created or asset logged in Atomicwork is recorded against the person who did it.

Helpdesk

Atomicwork MCP connector

The Atomicwork connector lets Claude, ChatGPT, Cursor, 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.

Connect on Elaichi How to connect

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.

37 tools

How to connect

How to connect Atomicwork to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Atomicwork once

Open Connections, choose Add connection, and pick Atomicwork.
Optionally set Share with to give a team access, then press Connect.
Paste an Atomicwork API key. One person generates a token in Atomicwork 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.

atomicwork

All categories

Atomicwork

Acquire

Ada

CM Mobile Service Cloud

Crisp

Desk365

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.

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 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.

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.

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.

Connect Atomicwork on Elaichi See pricing

Use cases

What teams do with Atomicwork through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

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.”

See all 37 Atomicwork tools below

Compare

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.

Elaichi compared with Zapier MCP and Composio for Atomicwork, by what to check
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	$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

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.

See it in Elaichi

What connecting Atomicwork gets you

6 screens from the product, each doing one job for your Atomicwork account.

The agent

Ask about requests, get real answers.

Type a question in plain language and read live Atomicwork requests and assets.

requests
assets
changes
workspace members

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 or Cursor

MCP clients

One endpoint reaches Atomicwork from anywhere.

Claude, ChatGPT and Cursor connect over OAuth, no SDK, no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

37 Atomicwork tools ready on connect.

Requests, assets, changes and workspace members are covered without custom code.

List all Atomicwork service catalog categories
List all Atomicwork forms requests
Create a Atomicwork request
List all Atomicwork assessment forms

ElaichiTools

Tool	Action	Description
List all Atomicwork service catalog categories	List	List all service catalog categories in an atomicwork workspace. Returns: id, name, item_count, archived, created_at. Required: workspace_id.
List all Atomicwork forms requests	List	List request form fields for requests in atomicwork. Returns form field data from the `data` array. Requires at least one of: `request_id`, `service_item_ids`, a combination of `channel_id` + `channel_type` + `request_form_type`, or `workspace_id` + `request_form_type`.
Create a Atomicwork request	Create	Create a new request in atomicwork. Returns the created request object including id, display_id, subject, status, and priority.
List all Atomicwork assessment forms	List	Get the assessment form associated with a specific problem in atomicwork. Returns the assessment form data object. Required: workspace_id, problem_id.
Create a Atomicwork assessment form	Create	Submit an assessment form for a specific problem in atomicwork. Required: problem_id.

Toolboxes

Every team gets its own toolbox.

Curate Atomicwork toolboxes per team so IT, HR and support see their scope.

IT service desk
HR operations
Change management
Asset management

ElaichiToolboxes

Name	Source template	Tools	Created
IT service desk toolbox Atomicwork · requests and assets	Atomicwork starter	18	Mar 4, 2026
HR operations toolbox Atomicwork · onboarding requests and forms	—	9	Mar 2, 2026
Change management toolbox Atomicwork · changes and approvals	—	24	Feb 27, 2026
Asset management toolbox Atomicwork · assets and assignments	Atomicwork starter	6	Feb 19, 2026
Service catalog toolbox Atomicwork · catalog items and categories	—	31	Jan 30, 2026
Compliance toolbox Atomicwork · audit logs and assessment forms	—	12	Jan 22, 2026

Shared connections

Teammates use Atomicwork without a credential.

See who connected each account and how many teams and members share it.

IT service desk
HR operations
Facilities
Change board

ElaichiConnections

Connection	Scope	Status	Access
AT Atomicwork (IT service desk) Connected by Emily Carter	Personal	• Active	1 team · 6 members
AT Atomicwork (HR operations) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
AT Atomicwork (Facilities) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
AT Atomicwork (Change board) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
AT Atomicwork (Asset team) Connected by Ryan Hayes	Personal	• Active	Not shared
AT Atomicwork (Compliance) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Answer who touched which request.

Append-only rows record when, who, what happened, type and resource in Atomicwork.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter emily.carter@northwind.io	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan jake.morgan@northwind.io	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks megan.brooks@northwind.io	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed tyler.reed@northwind.io	Atomicwork Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes ryan.hayes@northwind.io	Atomicwork Requests Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker ashley.parker@northwind.io	Atomicwork Requests List	Toolbox

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 works your Atomicwork queue.

Fetch requests, group them, draft a digest, approve it, post it back.

Atomicwork digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

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 Michael Brennan

Approve Deny
Post the digest

Atomicwork

Queued

Collections and dashboards

Atomicwork request health, computed on schedule.

Four metrics, 14 days of requests created and a breakdown by team.

Atomicwork health

Refreshed 4 minutes ago · every 15 minutes · from the requests collection

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

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, 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 blocking deleting them or editing workspace members. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt, however worded, can reach it.

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, 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, 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 on Gold, no credit card. Connect it once and pick what each team can call.

Connect Atomicwork Talk to us

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.