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

# Claude (claude.ai)

> Connect NexSpace to claude.ai and Claude Desktop as a custom connector

# Claude Custom Connector

Connect NexSpace to Claude so your team can read schedules, analytics, CRM,
and compliance data — and take governed actions — from any Claude
conversation. One connector, your whole workspace, with NexSpace approvals
and guardrails around every action.

## Add the connector

1. In claude.ai (or Claude Desktop), open **Settings → Connectors → Add custom connector**
2. Enter the NexSpace MCP endpoint:

```
https://mcp.nexspace365.com/mcp
```

3. Click **Connect**. Claude discovers the NexSpace authorization server
   automatically (OAuth 2.1 with Dynamic Client Registration — no client ID
   to paste) and opens the NexSpace consent page.
4. Log in with your NexSpace dashboard account and review the requested
   permissions, then **Allow access**.

That's it — Claude now lists the NexSpace tools in the conversation.

## What Claude can access

The consent page shows exactly what is being granted, grouped by domain with
a **Read** or **Write** badge per permission:

* **Default (no scopes requested):** the read-only bundle — every read
  permission, no writes, no connected-apps access. The consent page shows
  *"Read-only connection"*: Claude can view data but can never change
  anything.
* **Write access** (e.g. `crm:write`): lets Claude create and edit records.
  Medium-and-higher-risk writes **do not execute immediately** — they create
  an approval in NexSpace, your admins are notified, and the action runs only
  after a human approves it (see below).
* **Connected apps** (`apps:read` / `apps:write`): lets Claude reach the
  third-party apps you've connected to NexSpace (Slack, QuickBooks, HubSpot,
  …) through the same governed connector. Only apps with an active connection
  on your Integrations page are visible.

Your role, suite entitlements, and organization AI guardrails always apply on
top of the granted scopes — a scope can never exceed what your account can do
in the dashboard.

## How approvals work

When Claude attempts a gated action, the tool call returns:

```json theme={null}
{ "status": "pending_approval", "approvalId": 123 }
```

NexSpace notifies your facility admins, who review the action (with its full
arguments) under **Admin → AI Configuration → Approvals**. Once resolved,
Claude can check the outcome with the `get_approval_status` tool — including
the execution result after an approval, or the rejection reason.

`get_approval_status` is a read-only tool in the `general` category, so it
requires **`general:read`** — not "any caller". That scope ships in the default
read-only connector bundle, so an ordinary connection already has it; if you
grant write scopes, keep `general:read` granted too or Claude will be able to
submit actions it cannot poll. The tool is self-scoped: only approvals the same
caller submitted are visible.

## Revoke access

Remove the connector in Claude's settings, or revoke the grant from NexSpace
(Security settings → connected applications). Revocation takes effect
immediately; refresh tokens are rotated and reuse is detected.

## Troubleshooting

| Symptom | Fix |
| - | - |
| "Insufficient credential scope" | The action needs a scope the connection wasn't granted. Reconnect and grant it, or ask an admin. |
| "No active «app» connection" | Connect that app on **NexSpace → Integrations** first, then retry. |
| An action never runs | It's probably awaiting approval — check **Admin → AI Configuration → Approvals**. |


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