Connect an AI assistant
The MCP server is in beta. You can use it, but its tools, limits and behavior can still change. The changelog announces changes.
Any AI assistant that supports remote MCP servers with OAuth can connect. Propeller tests with Claude, Claude Code and ChatGPT.
Prerequisites
- A Propeller Backoffice account. The assistant gets at most the roles of this account.
- An AI assistant that supports remote MCP servers:
- Claude: every plan. On Free you can add one custom connector. On Team and Enterprise an owner adds the connector for the organization first, after which every member connects with their own account.
- ChatGPT: a paid plan that allows custom MCP servers. In Business, Enterprise and Edu workspaces an admin allows them first. Some personal plans only allow actions that read.
- A test tenant, if you have one, to try changes on first.
Add the server
The server address is the same for every assistant:
https://mcp.helice.cloud/mcp
Claude
In Claude on the web or the desktop app, open Settings > Connectors, choose Add custom connector and enter the address. Leave the advanced settings empty: the server supports dynamic client registration, so Claude registers itself and there is no client ID to create. On Team and Enterprise an owner adds the connector once under Organization settings > Connectors, after which members connect it from Settings > Connectors.
In Claude Desktop, add the server through Settings > Connectors only. Claude Desktop rewrites claude_desktop_config.json when it starts, so changes made directly in that file are lost.
ChatGPT
On chatgpt.com, open Plugins, choose Add custom MCP server and enter the address. Choose OAuth as the authentication and leave the client ID and secret empty. Adding the server is done in the browser.
ChatGPT asks for confirmation before it runs an action that changes data, on top of the server's own previews.
Claude Code
claude mcp add --transport http propeller https://mcp.helice.cloud/mcp
Then run /mcp in an interactive Claude Code session and choose the server to sign in.
Other MCP clients
Point the client at the server address. The server publishes OAuth protected resource metadata (RFC 9728), so a client that implements MCP authorization finds the authorization server and starts the sign-in by itself. Clients register with dynamic client registration or with a client ID metadata document and use the authorization code flow with PKCE.
Sign in and choose access
When you connect, the assistant opens the Propeller sign-in page in your browser. The page is available in English, Dutch, German and French. Nothing is stored until you press Allow.
-
Sign in with your Backoffice account, including your authentication code when your account uses one.
-
Choose the tenant. Everything the assistant does stays in this tenant.
-
Choose what the assistant may do:
Choice What the assistant can do with categories Read only Find and show catalogs, categories, texts and products. No changes. Edit products Also write texts, rename, move, hide or show categories, link products and clusters and change their order. Match my access Everything your own roles allow, including creating and deleting categories, which needs Owner on Product Data. Custom Viewer, Editor or Owner per module. -
Check the summary and press Allow. The page shows the tenant, the access and the address the app returns to.
Check the connection
Ask the assistant which tenant it works in. It calls whoami, which returns the tenant, the app and the effective access per module:
{
"sub": "member-live-4f2a9c1e-8b3d-4c7e-9a10-2b6d5e8f0c34",
"oidcScopes": ["offline_access", "openid", "email"],
"app": "connected-app-live-91d0c2f4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"tenant": "acme-office-b2b-x7k2q",
"permissions": [
{ "module": "product", "label": "Product Data", "user": "OWNER", "agent": "EDITOR", "effective": "EDITOR" },
{ "module": "pricing", "label": "Pricing", "user": "EDITOR", "agent": "VIEWER", "effective": "VIEWER" },
{ "module": "order", "label": "Order Data", "user": "VIEWER", "agent": "VIEWER", "effective": "VIEWER" }
]
}
user is the user's own role, agent is what they granted the assistant and effective is the lower of the two.
Disconnect
Ask the assistant to disconnect from Propeller, which calls the disconnect tool, or remove the connector in the assistant. Disconnecting deletes the stored login for that connection only. The same user's other apps stay connected.
To switch to another tenant or change the access, disconnect and connect again.