> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-agents/mcp-server/tools-reference/workspace-tools.md).

# Workspace tools

Workspace tools let your agent manage the things around your data: credentials, projects and folders, and — for admins — users, org settings, customizations, and activity exports. There's also a single `delete` tool for removing assets. These are available when you connect over [OAuth](/carto-for-agents/mcp-server/connecting-with-oauth.md). Some are open to any member; others (managing users, org settings, superadmin operations) require the matching permission on your CARTO account.

## Users

### `manage_users`

**Title:** Manage Users

**Manages organization members** — list, invite, remove, and handle invitations.

**Method:** `list` · `invite` · `delete` · `list_invitations` · `resend_invitation` · `cancel_invitation`

| Parameter                            | Type                             | Required     | Description                                             |
| ------------------------------------ | -------------------------------- | ------------ | ------------------------------------------------------- |
| `search` / `role_filter`             | string                           | No           | Filter the member list.                                 |
| `emails`                             | array                            | For `invite` | Members to invite.                                      |
| `role`                               | `Builder` \| `Viewer` \| `Guest` | For `invite` | The role granted on acceptance.                         |
| `userId` / `resourcesReceiverUserId` | string                           | For `delete` | The member to remove, and who inherits their resources. |

*Can modify data.*

## Credentials

### `manage_api_access_tokens`

**Title:** Manage API Access Tokens

**Lists, inspects, creates, and updates API Access Tokens** — the credentials for spatial apps and token-based MCP connections. To remove one, the agent uses [`delete`](#delete).

**Method:** `list` · `get` · `create` · `update`

| Parameter | Type   | Required               | Description                                                                              |
| --------- | ------ | ---------------------- | ---------------------------------------------------------------------------------------- |
| `id`      | string | For `get`, `update`    | The token.                                                                               |
| `body`    | object | For `create`, `update` | Grants (connection + source), allowed APIs, and optional referers, name, and expiration. |

*Can modify data.*

### `manage_oauth_clients`

**Title:** Manage OAuth Clients

**Lists, inspects, creates, and updates OAuth clients** — the SPA and M2M clients used to sign spatial apps and MCP hosts in. To remove one, the agent uses [`delete`](#delete).

**Method:** `list` · `get` · `create` · `update`

| Parameter | Type           | Required               | Description                                                          |
| --------- | -------------- | ---------------------- | -------------------------------------------------------------------- |
| `type`    | `spa` \| `m2m` | For `list`             | Which clients to list.                                               |
| `id`      | string         | For `get`, `update`    | The client.                                                          |
| `body`    | object         | For `create`, `update` | The client definition. Note that `update` replaces the whole client. |

*Can modify data.*

## Projects

### `organize_projects`

**Title:** Organize Projects

**Organizes maps and Workflows into projects and folders** — list, get, create, update, and move items.

**Method:** `list` · `get` · `create` · `update` · `add_item` · `move_item` · `rename_folder`

| Parameter | Type                   | Required                           | Description                                                 |
| --------- | ---------------------- | ---------------------------------- | ----------------------------------------------------------- |
| `id`      | string                 | For most methods                   | The folder or item to act on.                               |
| `body`    | object                 | For `create`, `update`, `add_item` | The folder or item payload.                                 |
| `kind`    | `folder` \| `shortcut` | For `add_item`, `move_item`        | Whether the item is a subfolder or a map/Workflow shortcut. |

*Can modify data.*

## Org settings and activity

### `admin_carto`

**Title:** Organization Administration

**Reads and applies org admin configuration and usage.** Gets settings, applies or diffs a settings bundle, and reads agent status, available models, and org stats.

**Method:** `get_settings` · `apply_settings` · `diff_settings` · `agents_status` · `list_agent_models` · `org_stats`

| Parameter  | Type   | Required                              | Description                                                                           |
| ---------- | ------ | ------------------------------------- | ------------------------------------------------------------------------------------- |
| `sections` | array  | No                                    | Which settings sections to read (for `get_settings`).                                 |
| `bundle`   | object | For `apply_settings`, `diff_settings` | Settings keyed by section (basemaps, palettes, maps, connections, workflows, and AI). |

*Can modify data: `apply_settings` changes org configuration.*

### `admin_carto_customizations`

**Title:** Manage Custom Basemaps

**Manages the org's custom basemaps** — list, get, create, and delete.

**Method:** `list` · `get` · `create` · `delete`

*Can modify data.*

### `export_activity_data`

**Title:** Export Activity Data

**Exports the organization's activity data for auditing**, then tracks the job. `body` selects the categories (activity, API usage, user list, group list), the format (CSV or Parquet), and the time range.

**Method:** `submit` · `status`

*Exports org data.*

### `superadmin_carto_resources`

**Title:** Organization Resources (Superadmin)

**Lists, transfers, or batch-deletes resources belonging to any user in the org.** Requires the elevated superadmin role.

**Method:** `list` · `transfer` · `batch_delete`

*Can modify data: transfer and batch-delete change ownership or remove resources.*

***

## Deleting assets

### `delete`

**Title:** Delete Asset

**Permanently deletes one CARTO asset.** A single tool covers every deletable asset type, selected by `kind`.

**Kind:** `map` · `workflow` · `connection` · `named_source` · `oauth_client` · `token` · `project_item`

| Parameter   | Type                   | Required           | Description                                               |
| ----------- | ---------------------- | ------------------ | --------------------------------------------------------- |
| `id`        | string                 | Yes                | The asset to delete (a connection also accepts its name). |
| `item_kind` | `folder` \| `shortcut` | For `project_item` | Whether the project item is a folder or a shortcut.       |

*Can delete data. To remove a user, the agent uses* [*`manage_users`*](#manage_users) *instead, so resources can be reassigned.*

{% hint style="warning" %}
`delete` is permanent. On hosts that ask for confirmation before destructive actions, the agent surfaces the request; CARTO annotates this tool as destructive so hosts can prompt.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-for-agents/mcp-server/tools-reference/workspace-tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.