Skip to main content

AI assistants (MCP)

Beta

The MCP server is in beta. You can use it, but its tools, limits and behavior can still change. The changelog announces changes.

The Propeller MCP server lets AI assistants such as Claude and ChatGPT work in a tenant on behalf of a Backoffice user. The user describes a job in plain language, for example "write a Dutch meta description for every category under Office supplies", and the assistant carries it out through the MCP server, with the user's own roles.

The MCP server covers category management: finding categories and their texts per language, placing products and clusters in categories, their order and the category tree.

https://mcp.helice.cloud/mcp

How it works​

  1. You add the MCP server to your AI assistant once.
  2. The assistant sends you to the Propeller sign-in page. You sign in with your Backoffice account, choose a tenant and choose what the assistant may do.
  3. The assistant calls the server's tools to read and change data. Every call runs as you, in that tenant, with the lower of your own roles and the access you granted.
┌───────────────────────────────────────────────────────────────┐
│ AI assistant │
│ Claude, ChatGPT, Claude Code or another MCP client │
└───────────────────────────────┬───────────────────────────────┘
│
│ MCP over HTTPS, OAuth 2.1
▼
┌───────────────────────────────────────────────────────────────┐
│ Propeller MCP server (mcp.helice.cloud/mcp) │
│ │
│ Category tools, previews, access checks, audit trail │
└───────────────────────────────┬───────────────────────────────┘
│
│ as the signed-in user
▼
┌───────────────────────────────────────────────────────────────┐
│ Propeller platform │
│ │
│ The user's roles are checked on every request │
└───────────────────────────────────────────────────────────────┘

What an assistant can do​

JobExample requestTools
Find and check"Which categories under Office supplies have no products?"list_catalogues, search_categories, search_products, list_category_products
Write category texts"Write a Dutch meta description for every category under Office supplies, at most 155 characters, based on its description."update_category, set_category_texts
Place products and clusters"Put all Leitz products in Office supplies > Filing and make it their main category."link_products, order_category_products
Manage the category tree"Under Office supplies, create Own brand with subcategories Paper and Pens, in Dutch and English."create_categories, update_category, delete_categories

Tools lists every tool with the access it needs.

Key concepts​

  • The assistant acts as the user. Every call carries the user's identity and Propeller checks the user's roles on every request. The assistant can never do more than the user can do in the Backoffice.
  • One tenant and one grant per connection. The user picks the tenant and the access when they connect. Each app a user connects has its own sign-in, tenant and access.
  • Catalogs and channels. Each channel uses a catalog, the root category of a category tree. Channels can share a catalog. Tools name a category by id or by path, for example Office supplies > Paper > Copy paper.
  • Previews before changes. Every tool that changes data has a dry run. A rename, move, reorder or hide and show of items the user named can follow a matching dry run directly. Every other change waits for the user's yes. See Changes and confirmations.
  • Everything is recorded. Each sign-in and each tool call is logged with the user's email address, the tenant and the app.
  • Assistants and agents. An agent from Workflows and AI agents is embedded in Propeller and calls your webhook. An AI assistant works the other way round: it runs in the user's chat or coding app and calls Propeller through the MCP server.

See also​