> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://support.atomicwork.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://support.atomicwork.com/_mcp/server.

# Managing tools for AI Coworkers

> Connect MCP servers, choose who can use each tool, and enable tools on an AI Coworker.

AI Coworkers act through **tools** provided by **MCP servers**. You manage those servers in the **MCP store**, then choose which tools each AI Coworker can use.

There are two places to do this:

* The **MCP store**, where you connect a server, enable its tools, choose who can use them, and add pre-call or post-call scripts.
* The coworker's **Tools** tab, where you turn tools on or off for that AI Coworker and choose whether a tool runs as the coworker or as the user.

Connecting a server does not give every coworker access to it. A tool has to be enabled in the MCP store, included in **Available for**, and turned on for the coworker.

## Open the MCP store

Go to **AI Workforce > AI Registry > MCP store**.

The store lists every MCP server available to your workspace. Use the **All**, **Connected**, and **Not connected** tabs to filter the list, or use the category list and the search field to find a server. Click **Add MCP server** if you want to add a custom server.

![The MCP store, with All, Connected, and Not connected tabs, category filters, and an Add MCP server button](/_fern-files/_img/48b65241b552c69eafb93ed3aea56dc46b48e3265ab5e23b22525344825088ad.webp)

## Connect a server

Open an unconnected server to start setup. A **Setup** dialog asks for the credentials that server needs — the fields vary, for example Client ID, Client secret, and Client URL. Click **Test**, then **Connect**.

![The Setup dialog for an unconnected MCP server, with credential fields and Test and Connect buttons](/_fern-files/_img/e84b924c0e0e5141f1e6a8344e9bad44ca1f54b2cf1f8cef23bb55b451409d0a.webp)

Once a server is connected, its page shows a header with **Connected by**, **Last updated**, **Connected to**, and **Status**.

To add your own server when it is not in the catalog, see [Custom MCP](https://support.atomicwork.com/integrations/mcp-store/custom-mcp).

## Review tools on a server

Open a connected server to see its **Tools** section. You can search the list, and filter it by **All tools**, **Enabled**, or **Not enabled**.

Tools are grouped automatically into collapsible **Read**, **Write / Delete**, and **Other** sections, each with a tool count.

![The Tools section on a connected MCP server, with tools grouped under Read and a filter set to All tools](/_fern-files/_img/2698c7cb7610bdf2e8b5e4557e4e2de9704fd056831b7630004e2c1a02b84d61.webp)

Each group header has an **Available for** dropdown and a toggle for the whole group. If the tools in the group have mixed settings, **Available for** shows **Custom**.

Each tool row has a name, a description, an **Available for** dropdown, an enable switch, and a ⋮ menu.

### Choose who can use a tool

Use **Available for** to control who can use a tool or a group of tools. It is a multi-select. The options include **All users**, **All AI Coworkers**, and per-workspace coworker segments, such as **Default workspace Coworkers**.

![The Available for dropdown on a tool, showing All users, All AI Coworkers, and per-workspace coworker segments](/_fern-files/_img/093c236e66e64b859c28e7be00d73dba6b5b7a6063fa227f0fe41690eb8a7143.webp)

> **Tip**
>
> Set **Available for** on the group header when you want the same access for every tool in that group. To treat tools differently, set **Available for** on the individual rows.

### Enable or disable tools

Use the switch on a tool row to turn that tool on or off, or use the switch on the group header to turn the whole group on or off.

**Write / Delete** tools are often off by default, but not always. Check the switches before you rely on the default.

We'd recommend starting with **Read** tools and turning on **Write / Delete** tools only when a coworker needs them.

## Add a pre-call or post-call script

Open the ⋮ menu on a tool row to add a script that runs on every call:

* **Add pre-call script** — use to validate or redact before each call.
* **Add post-call script** — use to mask or log after each call.

![The more-actions menu on a tool, showing Add pre-call script and Add post-call script](/_fern-files/_img/0e5ca55c19e4bda65105ece3f657686e867f64137a05bedd4cd1bb0ded3bcf48.webp)

Because these scripts run as code rather than as instructions, they apply the same way on every call.

## Enable tools on an AI Coworker

After a server is connected, open the AI Coworker and go to its **Tools** tab: **AI Workforce > AI Coworkers > \[coworker] > Tools**.

The tab lists the connected MCP servers, each with how many of its tools are enabled for this coworker, for example *28 of 527 enabled*. Search for a server or tool, or use the categories on the left to narrow the list.

![The Tools tab on an AI Coworker, with connected MCP servers collapsed and a count of enabled tools on each](/_fern-files/_img/6cadc1fb8b331ee2b6eceab43b92a39098981894358040bb76e45a5fc060f08c.webp)

Expand a server to see the same **Read** and **Write / Delete** groups. Turn each tool on or off for this coworker, or use the toggle on a group header to change the whole group.

The coworker's **Overview** card summarises this as **Tools enabled**, with the number of tools enabled across its MCP servers.

> **Note**
>
> The **Atomicwork** MCP server is enabled by default on every new AI Coworker, so it can post notes, change status, and look up requests. Leave this server enabled.

### Choose how a tool runs

On the coworker's **Tools** tab, each tool row and each group header has **Run as AI coworker** and **Run as user**. Use these to choose whether the tool runs as the AI Coworker or as the user.

![An expanded MCP server on a coworker's Tools tab, with Run as AI coworker and Run as user on each tool](/_fern-files/_img/914f35f0d9863882ab3dd406aa2fd396cb419c68a842171fa3acf864db184a4b.webp)

## Related

* [Setting up an AI Coworker](https://support.atomicwork.com/documentation/ai-workforce/setting-up-an-ai-coworker)
* [Understanding AI guardrails in Atomicwork](https://support.atomicwork.com/guides/understanding-ai-guardrails-in-atomicwork)
* [Code library](https://support.atomicwork.com/documentation/ai-workforce/code-library)
* [Custom MCP](https://support.atomicwork.com/integrations/mcp-store/custom-mcp)