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

Source: https://elaichi.ai/connectors/atomicwork/

## Facts

| | |
| --- | --- |
| Application | Atomicwork |
| Category | Helpdesk |
| AI tools | 37 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. 37 tools is past the 30-tool threshold, so clients use `search_tools` and `execute_tool` |

## What you can ask once Atomicwork is connected

- Show open Atomicwork requests by workspace this week.
- Create an Atomicwork request for a replacement laptop.
- List Atomicwork assets assigned to the support team.

## Connect Atomicwork in Elaichi

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

1. Open Connections, choose Add connection, and pick Atomicwork.
2. Optionally set Share with, then press Connect.
3. 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.

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

## Connect Atomicwork to 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.

## Connect Atomicwork to 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.

## Connect Atomicwork to 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 Atomicwork 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 Atomicwork 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 Atomicwork through Elaichi

### Raise a request while still on the call

IT service desk. 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.

### Catch a request up after the fix

IT service desk. 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.

### See what is open and how urgent

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

### Log new hardware the day it arrives

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

### Draft a change record before the maintenance window

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

### Answer who did what in Atomicwork

Security and compliance. 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.

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

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

## All 37 Atomicwork tools

Every tool below is callable through https://api.elaichi.ai/mcp once Atomicwork is connected, subject to the toolbox it is in and the restrictions on the caller.

- **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.
- **List all Atomicwork assets** (List). List all assets in atomicwork. Returns a paginated array of asset objects under the data field.
- **Create a Atomicwork asset** (Create). Create a new asset in atomicwork. Required: asset_type_id and form_fields containing the asset's attributes such as display_name, serial_number, status, and assigned_to.
- **Create a Atomicwork change management change** (Create). Create a change request in atomicwork. Accepts fields such as subject, change_type, status, priority, urgency, impact, requester, and custom_fields to populate the new change record.
- **List all Atomicwork workspaces** (List). List all atomicwork workspaces. Returns: id, name, type, description, is_default, member_count, created_at.
- **List all Atomicwork requester entities** (List). List requester entities available for REQUEST forms in atomicwork. Returns: id, label, value, deactivated for each entity.
- **List all Atomicwork audit logs** (List). List audit logs in atomicwork. Returns log entries including id, event_type, module, event_at, and log_text, along with actor user details. Required: server.
- **List all Atomicwork workspace members** (List). List all members of an atomicwork workspace. Returns a collection of workspace member objects. Required: workspace_id.
- **Update a Atomicwork workspace member by ID** (Update). Update a workspace member in atomicwork by id. Required: workspace_id and id.
- **List all Atomicwork service catalog items** (List). List service catalog items in Atomicwork for a specific workspace and category. Returns items from the service catalog. Required: workspace_id, category_id.
- **Get single Atomicwork requests ID by ID** (Get). Get a single request by id in Atomicwork. Returns the full request object for the specified workspace. Required: workspace_id, id.
- **Get single Atomicwork requests number by ID** (Get). Get a specific request in Atomicwork by id. Returns the full request object. Required: id.
- **Atomicwork requests number partial update** (Update). Partially update an existing request in Atomicwork by id. Returns the updated request object. Required: id.
- **Delete a Atomicwork requests number by ID** (Delete). Delete a specific request in Atomicwork by id. Returns an empty response on success. Required: id.
- **Create a Atomicwork requests v 2** (Create). Create a new request in Atomicwork. Returns the created request object.
- **List all Atomicwork requests search** (List). List and search requests in an atomicwork workspace. Returns request data from the specified workspace. Required: workspace_id.
- **List all Atomicwork requests count** (List). Get the total count of requests in an atomicwork workspace. Returns the aggregate count of requests matching the query. Required: workspace_id.
- **List all Atomicwork request views** (List). List request views in atomicwork. Returns a collection of request view objects available in the system.
- **List all Atomicwork request priority options** (List). List available request priority options in atomicwork for a given workspace. Returns priority option records from the workspace. Required: workspace_id.
- **Create a Atomicwork request activity note** (Create). Create an activity note on an atomicwork request identified by its display ID. Required: display_id.
- **List all Atomicwork request trash** (List). List trash entries associated with a specific atomicwork request. Required: display_id.
- **List all Atomicwork user lists** (List). List all lists associated with a specific user in an atomicwork workspace. Returns the collection of user list records. Required: workspace_id, user_id.
- **Update a Atomicwork problem task by ID** (Update). Update a task belonging to a specific problem in atomicwork. Required: problem_id and id.
- **Get single Atomicwork assets ID by ID** (Get). Get a single asset by id in Atomicwork. Returns the asset object. Required: id.
- **Update a Atomicwork assets ID by ID** (Update). Update an existing asset by id in Atomicwork. Required: id.
- **List all Atomicwork assets search** (List). List and search assets in Atomicwork. Returns a collection of asset records from the data field of the response.
- **Get single Atomicwork change management changes number by ID** (Get). Get a specific change management change in atomicwork by id. Returns the full change record. Required: id.
- **Atomicwork change management changes number partial update** (Update). Partially update a change management change in atomicwork by id. Sends a PATCH request to modify one or more fields on the specified change record. Required: id.
- **Create a Atomicwork change management changes create with file** (Create). Create a new change management change record with file attachments in atomicwork. Submits a multipart form payload to include both change metadata and associated files in a single request.
- **Create a Atomicwork change trash** (Create). Move a change to trash in Atomicwork change management. Required: display_id.
- **List all Atomicwork change activity notes** (List). List activity notes for a specific change in atomicwork. Returns a collection of activity note records associated with the change. Required: change_id.
- **Create a Atomicwork user** (Create). Create a new user in atomicwork via the settings API. Returns the created user object.
- **Create a Atomicwork attachment** (Create). Create an attachment in atomicwork by submitting a multipart form data request to upload a file.