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

# Connect ChatGPT or Claude to Presolve

> Connect an approved AI application, choose its access, and manage your connection.

Connect ChatGPT or Claude to your firm's Presolve account to find cases, check tasks, and use supported actions with your Presolve permissions. Your administrator must register the application and enable access for your role.

## Before you connect

The production MCP server address is:

```text theme={null}
https://www.presolve.com/api/mcp
```

Ask your administrator for the application's registered client ID and the access your firm has approved. Each application uses a separate registration.

Your role needs **Connect MCP**, **View cases**, **View all cases**, unrestricted case visibility, and the data permissions needed for the requested access. Changes also require **Allow MCP changes** and the corresponding action permissions. Integration-management permission is not required. Existing non-admin roles are not automatically enabled.

> [!NOTE]
>
> Restricted-case roles cannot currently connect. Connecting an application does
> not give your account additional permissions or access to another firm.

## Connect your application

**ChatGPT**

1. Open your workspace's custom app or connector setup. Your workspace may
   require an administrator to add the application. 2. Enter the production
   server address and choose OAuth with the client ID supplied by your
   administrator. Presolve's public client uses PKCE without a client secret;
   OIDC is not needed. 3. Have the administrator register the exact callback
   address shown by ChatGPT for this app. 4. Connect or reconnect the Presolve
   app and continue to Presolve to sign in and review access.

**Claude**

1. Open **Customize → Connectors** and add a custom connector named
   Presolve. 2. Enter the production server address and select Streamable HTTP
   where a transport choice is shown. 3. Choose **Use your own OAuth client**
   and enter the registered client ID. Leave the client secret blank for the
   approved public client. 4. Select **Connect** to sign in to Presolve and
   review access. Your administrator must register Claude's exact callback
   address.

On Presolve's consent page:

1. Verify the application, account, and firm.
2. Review every requested permission. **View only**, **View and change**, and **Make changes** describe different access.
3. If write access is requested, decide whether to select **Allow supported actions on my behalf**. This option is off by default.
4. Select **Allow connection**, or **Cancel** if the request is unexpected.
5. Return to the AI application. Refresh its tools or start a new conversation if it still shows the previous tool list.

Your password and the connection's internal API credential are not shared with the application. It receives tokens limited to the approved access. Data returned by tools is shared with that application, so use your firm's approved applications and data-handling practices.

## Why do I only see case tools?

If consent shows only **Cases — View only**, the application requested only case-read access. It will not receive task access or write tools just because your administrator allowed them in the registration.

Ask the administrator to configure the requested scopes, then reconnect and approve the broader permissions. Existing tokens do not gain scopes automatically. There is no fixed nine-tool limit: the available tools depend on your connection's approved access, your role, and enabled features.

## What can the application do?

Depending on approved access, shared Presolve tools cover case search and context, notes and communications, tasks, calendars, deadlines, documents, contacts, reporting, team members, case activity, and supported actions. They use the same underlying tool and access services as Presolve's assistant.

| Connection authority | Behavior |
| - | - |
| Read access | Retrieves authorized information. |
| Write access without delegated execution | Creates review requests for supported changes; does not execute them automatically. |
| Write access with delegated execution | Eligible task, note, tag, call-log, and time-entry actions can execute without a separate Presolve confirmation. |
| Email, e-signature, financial and case-field changes, assignments, and workflow launches | Still require Presolve review where supported, even with full scope and delegation. |

Some actions and intake sections are unavailable through hosted MCP. **Full scope** means all supported MCP scopes, not every internal API or permission. The AI application may also ask for its own tool-use approval; that is separate from Presolve's consent and review requirements.

A response saying `approval_required` means the action has **not** executed. Follow its Presolve review link. If a change times out, check the record or review request in Presolve before trying again.

## Try a read-only query

After connecting, try:

* “How many active cases can I access? Return the count only.”
* “Show at most five tasks and tell me whether more results are available.”
* “Which team members are available in my firm?”

Task and team queries require their corresponding scopes. These checks do not verify write execution, token refresh, or revocation. Do not use a real send or financial action merely to test connectivity.

## Manage or disconnect

Open [My connections](https://www.presolve.com/oauth/mcp/connections). Each active connection has a **Disconnect** button. You can disconnect your own connections even after your MCP permission is removed.

An administrator can also revoke a **Managed MCP connection** from the organization's API Credentials list. Disconnecting stops subsequent requests and token refreshes; it does not erase information already received by the application.

Connections expire after **30 days**. Reconnect and approve the intended access to continue. When switching firms or accounts, review the identity shown during the new sign-in.

## Troubleshooting

| Message or behavior | What to check |
| - | - |
| Additional permission required | Ask an administrator to check membership, Connect MCP, requested data permissions, unrestricted case visibility, and Allow MCP changes for writes. |
| Application is not registered | Confirm the client ID and exact callback address with the administrator. |
| Sign-in returns 404 | Ask the deployment administrator to check the consent-page routing. |
| Only case tools appear after permissions were expanded | Reconnect with explicit requested scopes, review consent, then refresh the client's tools. |
| A connection stops working | Check role changes, expiry, revocation, disabled clients, and service availability. |
| The Presolve logo does not appear in the AI application | Some clients use their own app branding rather than the server's icon metadata. |

For operator setup, scope names, and technical limits, see the [MCP developer guide](https://www.presolve.com/docs/mcp.md). For separate API credentials, see [API keys](https://www.presolve.com/docs/help/integrations/api-keys.md).


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