This page is for the people who make the Spendesk assistant available to a team: the Spendesk Admin or Account Owner, and the administrator of the AI workspace (Claude, ChatGPT or Dust). It covers what each of them does, in order, and what users do next. For what the assistant can do once connected, see Connect an AI assistant (MCP).

Assistant	Plans	Who adds Spendesk	Where users connect
Claude	Free, Pro, Max, Team, Enterprise	Team and Enterprise: an Owner or Primary Owner. Other plans: each user	Customize → Connectors
ChatGPT	Business, Enterprise, Edu (web only)	A workspace admin or owner, who publishes the app	Apps menu of a chat
Dust	All workspaces	A workspace admin	The agents that use the tool

1. In Spendesk: create the connection

A Spendesk Admin or Account Owner does this once for the organisation, for each assistant:

Open Settings → Integrations → MCP (for an organisation with several entities, the MCP tab of the multi-entity hub).
Choose Claude, ChatGPT or Dust, and confirm with your second factor.
Spendesk shows the connection details: the server URL https://public-api.spendesk.com/v1/mcp, a client ID, a client secret, and the authorization and token endpoints.
Send them to the administrator of the AI workspace through a secure channel — the client secret is a password for your organisation's connector, not something to paste in a chat or a ticket.

The connection's Permissions tab sets what the connector may ask for, and changing it needs a new second-factor check; each user still picks their own permissions when they connect. Before allowing write permissions, read Assistant actions and safety.

2. In the assistant: add Spendesk

Claude Team and Enterprise

An Owner or Primary Owner of the Claude organisation:

Opens Organization settings → Connectors and clicks Add.
Chooses Custom → Web, and enters the server URL.
Opens Advanced settings and pastes the client ID and client secret.
Clicks Add.

Users then open Customize → Connectors, find Spendesk (labelled Custom), click Connect and approve the access in Spendesk. The first time Claude uses a Spendesk tool, it asks whether to allow it once, always, or not.

On Free, Pro and Max plans, each user adds the connector themselves from Customize → Connectors → Add custom connector, with the same URL, client ID and client secret.

Source: Claude Help Center, "Get started with custom connectors using remote MCP".

ChatGPT Business, Enterprise and Edu

Custom MCP apps in ChatGPT are in beta and web-only. Only admins and owners can publish an app to the workspace.

Turn on developer mode. On Business, each admin or owner turns it on for themselves, in Settings → Apps → Advanced settings, or when creating the app. On Enterprise and Edu, grant it under Workspace settings → Permissions & Roles → Connected Data, then turn it on in Settings → Apps → Advanced settings.
Create the app. In Workspace settings → Apps → Create, enter the Spendesk server URL, choose OAuth and fill in the client ID and client secret. Click Scan Tools, approve the access in Spendesk, then Create. The app is saved as a draft.
Test it from a chat, with the draft app selected.
Publish it from Workspace settings → Apps → Drafts → Publish. On Enterprise and Edu, the publish dialog lets you choose which Spendesk actions the app may use (Configure Actions) and which groups get it (Configure Access).

Users then select Spendesk in a chat and approve the access in Spendesk the first time. ChatGPT may ask for confirmation before a write action.

❗️
New Spendesk tools do not appear on their own
ChatGPT keeps a snapshot of the app's tools from when it was published. When Spendesk adds or changes tools — as when write actions arrived on 25 September 2026 — an admin has to update the app: on Enterprise and Edu, Workspace settings → Apps → ⋯ → Action control, then Refresh (new actions start disabled); on Business, recreate and republish the app.

Source: OpenAI Help Center, "Developer mode and MCP apps in ChatGPT".

Dust

A Dust workspace admin:

Opens Spaces → Tools → Add tools → Add MCP server.
Enters the Spendesk server URL and chooses static OAuth.
Fills in the client ID, client secret, authorization endpoint and token endpoint shown by Spendesk.
Adds the Spendesk tool to the agents that should use it.

Users approve the access in Spendesk the first time an agent uses it.

Dust can also register itself without a client from Spendesk (automatic set-up from the server URL). A connection registered that way only gets Spendesk's low-sensitivity permissions by default — companies, chart of accounts, cost centers, analytical fields and expense categories — so it cannot answer spend questions. Use the connection details from Spendesk instead.

Source: Dust documentation, "Adding an MCP Server".

Langdock

Langdock registers itself: add a remote MCP server with the Spendesk server URL, and Langdock opens the approval page. As for Dust's automatic set-up, such a connection only gets the low-sensitivity permissions by default.

3. Check the rollout

Ask a user to connect and try the questions in Check the connection. If a company is missing, the user is not a Controller or Account Owner there; if a tool is missing, the permission was not ticked — or, in ChatGPT, the app needs a refresh.

Assistant steps checked against each vendor's documentation on 29 September 2026. Their menus change often: if a step no longer matches, follow the linked source and tell us at [email protected].