> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decimal.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect AI tools

> Connect Claude, ChatGPT, Claude Code, Cursor, or VS Code to Decimal with MCP, and choose the access your client needs.

Connect your AI client to Decimal to investigate [support tickets](https://docs.decimal.app/support/overview.md), read knowledge, and review [knowledge gaps](https://docs.decimal.app/knowledge-base/kb-gap-detection.md).

To give Decimal access to another service's tools instead, see [MCP servers](https://docs.decimal.app/integrations/mcp.md).

## Before you connect

You need an **admin** or **member** role in the Decimal workspace you want to use. Playground users cannot connect with OAuth. Your AI client's account and workspace policies must also allow custom MCP connections.

OAuth gives both admins and members access to create tickets and approve or reject gaps. For a read-only connection, use a client that supports an API key and ask your Decimal admin for a key with only the read scopes you need.

Use this server URL with the **Streamable HTTP** transport:

```text theme={null}
https://api.getdecimal.ai/mcp
```

An admin can also open **Settings → API keys** in Decimal and find **MCP server**. Choose a client under **Setup** to copy its **Sign in** or **API key** configuration.

![Decimal's MCP setup shows separate sign-in and API-key commands for Claude Code, with Cursor and VS Code options beside it.](https://mintcdn.com/decimalai/dleq-5zJk7T2qhdM/images/mcp-client-setup.png?fit=max\&auto=format\&n=dleq-5zJk7T2qhdM\&q=85\&s=8f0bb19f25f37ea072a80a7c0c3e0ce0)

## Choose your client

> [tab] Claude
>
> 1. Open **Customize → Connectors** in Claude, then **+ Add → Add custom connector**.
> 2. Name the connector **Decimal** and enter `https://api.getdecimal.ai/mcp`.
> 3. Continue to the authentication settings. Use browser sign-in and **Use Claude's published identity (Recommended)** for the OAuth client.
> 4. Finish adding the connector. Sign in to Decimal and choose your workspace when prompted.
> 5. Return to Claude, connect Decimal, and enable it for your conversation.
>
> On Team or Enterprise, an authorized owner or administrator must first add it under **Organization settings → Connectors → Add → Custom → Web**. Members then connect individually.
>
> Claude's [connector guide](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp) covers account-specific setup. These steps use OAuth. Do not put a Decimal API key in a client-ID field or in a chat message.

> [tab] ChatGPT
>
> 1. Open ChatGPT's **Plugins** page.
> 2. Select the plus button, then **Add custom MCP server**.
> 3. Enter **Decimal** as the name and a description such as “Search Decimal support tickets and knowledge.”
> 4. Under **Connection**, enter `https://api.getdecimal.ai/mcp` as the public server URL.
> 5. Choose OAuth, review the access and risk warning, then select **Create as a plugin**.
> 6. Complete Decimal sign-in and workspace selection, then review the tools discovered.
> 7. Install the resulting plugin. Start a conversation and select it with `@`.
>
> If your workspace blocks custom servers, ask its administrator. Follow OpenAI's [connection guide](https://developers.openai.com/plugins/deploy/connect-chatgpt) for the current controls.
>
> Use OAuth for this setup. If the form asks for an OAuth client ID or secret you don't have, [email support](mailto:support@getdecimal.ai). A Decimal API key is not an OAuth client credential.

> [tab] Claude Code
>
> ### Sign in
>
> Run:
>
> ```bash theme={null}
> claude mcp add --transport http decimal https://api.getdecimal.ai/mcp
> ```
>
> Open `/mcp` in Claude Code, select Decimal, and authenticate. Choose your Decimal workspace in the browser.
>
> ### Use an API key
>
> Make `DECIMAL_API_KEY` available in your shell from a secure local secret source, then run:
>
> ```bash theme={null}
> claude mcp add --transport http decimal https://api.getdecimal.ai/mcp \
>   --header "Authorization: Bearer $DECIMAL_API_KEY"
> ```
>
> Your shell expands the variable before running the command. Treat the saved client configuration as containing a secret. Keep it out of source control and shared project files.
>
> Claude Code's [MCP guide](https://code.claude.com/docs/en/mcp) covers connection management.

> [tab] Cursor
>
> Add Decimal to `.cursor/mcp.json` for the project, or `~/.cursor/mcp.json` for your user.
>
> ### Use an API key
>
> Make `DECIMAL_API_KEY` available to the Cursor process, then add:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "decimal": {
>       "url": "https://api.getdecimal.ai/mcp",
>       "headers": {
>         "Authorization": "Bearer ${env:DECIMAL_API_KEY}"
>       }
>     }
>   }
> }
> ```
>
> Open **Customize** and enable the MCP server. If you set the environment variable after starting Cursor, restart it.
>
> ### Sign in
>
> Decimal's sign-in configuration is:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "decimal": {
>       "url": "https://api.getdecimal.ai/mcp"
>     }
>   }
> }
> ```
>
> This requires a Cursor version that supports Decimal's OAuth registration method, **CIMD**. Cursor's [MCP guide](https://cursor.com/docs/mcp) documents OAuth but does not establish CIMD compatibility. Use the API-key setup if registration fails.

> [tab] VS Code
>
> Add Decimal to `.vscode/mcp.json`, or use a private user-level MCP configuration.
>
> ### Sign in
>
> ```json theme={null}
> {
>   "servers": {
>     "decimal": {
>       "type": "http",
>       "url": "https://api.getdecimal.ai/mcp"
>     }
>   }
> }
> ```
>
> Start the server from VS Code's MCP controls and follow the browser sign-in prompt. Choose your Decimal workspace. Use VS Code 1.106 or later for [CIMD support](https://code.visualstudio.com/updates/v1_106).
>
> ### Use an API key
>
> Make `DECIMAL_API_KEY` available to the VS Code process, then add the header:
>
> ```json theme={null}
> {
>   "servers": {
>     "decimal": {
>       "type": "http",
>       "url": "https://api.getdecimal.ai/mcp",
>       "headers": {
>         "Authorization": "Bearer ${env:DECIMAL_API_KEY}"
>       }
>     }
>   }
> }
> ```
>
> Keep the environment reference in the file rather than replacing it with the key. VS Code's [configuration reference](https://code.visualstudio.com/docs/agents/reference/mcp-configuration) covers file locations and authentication.

## Limit an API key's access

Ask a Decimal admin to open **Settings → API keys → New API key**. Give the key a name that identifies its client and choose only the scopes it needs. The **Read only** shortcut selects read scopes; review that selection before creating the key. **All** also includes write and delete permissions for the public API.

![The New API key dialog has individual scope checkboxes and Read only and All shortcuts. No key has been created.](https://mintcdn.com/decimalai/dleq-5zJk7T2qhdM/images/mcp-api-key-scopes.png?fit=max\&auto=format\&n=dleq-5zJk7T2qhdM\&q=85\&s=c7624b1bcc5a306c61723764af8389eb)

For example, `tickets:read` and `knowledge:read` let a client investigate tickets and knowledge without changing them. Add `gaps:read` to inspect proposed changes or `pull_requests:read` to inspect pull requests.

Write permissions are separate:

| Scope | Action |
| - | - |
| `tickets:write` | Create a ticket |
| `tickets:notes` | Add an internal note to a ticket's originating helpdesk |
| `gaps:write` | Approve or reject a gap |

Copy a newly created key into secure storage when Decimal shows it. It is displayed only once. Keep it out of chat messages, screenshots, URLs, and source control.

## Check your workspace and tools

Check the workspace selected on the Decimal sign-in screen before authorizing the connection. Then ask:

> “List the Decimal tools I can use. Don't retrieve records or change anything.”

With OAuth, **members** can read tickets and files, knowledge articles, gaps, and pull requests. They can also create tickets and approve or reject gaps. **Admins** additionally have access to API-created conversations, automations and runs, and audit logs.

Internal-note creation through `create_ticket_note` requires an API key with `tickets:notes`; current OAuth role grants don't include that scope.

Decimal checks current workspace membership and role on each OAuth request. Don't assume an older OAuth connection stays read-only. API keys use their assigned scopes.

Tools also depend on workspace features. A tool can appear in the client and still return `forbidden` if the feature is unavailable.

Try a read-only question next:

* “Find tickets about a password reset loop. Open the relevant tickets and summarize the replies and internal notes.”
* “Find published knowledge articles about password resets and cite the steps.”
* “Show an in-review knowledge gap and explain its diff without applying it.”

Ticket search results show the original post. Ask the client to open a ticket when you need its replies and internal notes.

## Review changes before running them

Tell your client to show the proposed change and ask for confirmation before calling a write tool. Don't assume every client will ask automatically.

Creating a ticket can lead to email replies to the requester. Approving a knowledge gap can publish a live help-center change. Check the recipient or destination before confirming.

* **Create a ticket:** Review the requester email, title, and body before confirming `create_ticket`. Your workspace needs a connected mailbox; with multiple mailboxes, choose the intended one.
* **Add an internal note:** Review the ticket, originating helpdesk, and Markdown body before confirming `create_ticket_note`. The note is sent to the helpdesk and attributed to the API key's name. The helpdesk must support this action.
* **Approve a gap:** Inspect the diff and destination before confirming `approve_gap`. It applies an in-review knowledge change to an internal article or a connected Zendesk or Intercom help center. It doesn't approve code gaps.
* **Reject a gap:** Confirm the proposed change you want to discard before calling `reject_gap`. It rejects an in-review gap; it doesn't undo an applied change.

For example: “Prepare a ticket for \[requester email]. Show me the mailbox, address, title, and body, then ask before creating it.”

## Fix a connection problem

| What you see | What to check |
| - | - |
| The wrong workspace | Reconnect and check the selected workspace on the Decimal sign-in screen before authorizing access. |
| OAuth registration fails | Use a client with **Client ID Metadata Document (CIMD)** support. Decimal doesn't offer dynamic client registration (DCR). Update the client or use its API-key setup. |
| Sign-in works, then access returns `403` | Check your current membership and role in the selected workspace. Playground roles cannot connect. A revoked connection also blocks access. |
| A tool returns `forbidden` | Check the required scope and whether that workspace feature is enabled. An admin role doesn't turn on disabled features. |
| A tool is missing or returns “Unknown tool” | Refresh the client's tool list. Check OAuth role access or API-key scopes, including `tickets:notes` for internal notes. |
| An API key returns `401` | Check that the key is active and unexpired, and that the client process receives `DECIMAL_API_KEY` and sends the Bearer header. |
| Gap approval or rejection returns a conflict | Read the gap again. It must still be in review. Don't retry an already-applied or rejected change. |
| Gap approval returns a bad request | Check whether it is a code gap. Use its pull-request workflow instead. |
| A ticket file link expired | Request the file again. Keep signed download links private while they are valid. |
| Temporary authentication failure | Retry later. If it continues, send support the error and client version, never the key or token. |

If the error says **Reconnect and choose a workspace**, repeat sign-in and select the workspace. If it says **This connection was revoked**, [email support](mailto:support@getdecimal.ai) rather than assuming reconnecting will restore it.

## Disconnect when you're finished

Remove or disconnect Decimal in your AI client's settings.

For API keys, a Decimal admin can open **Settings → API keys**, open the key's options, and choose **Revoke API key**. Update every client using that key if you replace it.

For OAuth, **Connected teammates** shows active connections but has no self-service grant-revocation control. [Email support](mailto:support@getdecimal.ai) for help revoking access. Removing workspace membership blocks that user's OAuth access. Downgrading an admin to a member still allows ticket creation and gap approval or rejection.

## Know what your client receives

Tool results can include requester contact details, replies and internal notes, ticket files, knowledge drafts, gap diffs, and pull-request content. Admin tools can also return automation, API-conversation, and audit data.

Check your organization's data-sharing rules and your AI client's privacy settings before connecting. Review Decimal's [privacy policy](https://www.decimal.app/privacy). Disconnecting doesn't erase content already returned to the client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.