MCP server for AI agents
Connect an AI assistant (like Claude) to your Configo account so it can build and test-calculate a product configurator for you.
Configo runs an MCP server that lets an AI assistant work with your configurators directly — reading a product spec or spreadsheet you give it, creating the materials and controls/calculations/parts a configurator needs, and running test calculations to check the numbers come out right, all without you clicking through the visual editor yourself.
What it can do
Once connected, an assistant can:
- List your projects and the materials already defined in one
- Create new materials (fabrics, hardware, etc.) and update existing ones — refreshing prices from a new supplier price list, say
- Create, duplicate and delete configurators, and set their controls, calculations and parts
- Browse the public showcase and copy a configurator from it into your project
- Run a test calculation for a given set of inputs (e.g. a width/height/fabric combination) and get back the price and bill of materials it would produce, without creating a real order — one set at a time or several in a single request
- Read your orders, the products on them and the configurations they were built from, to check a configurator against what was actually sold
- Run the analytics reports (revenue, funnel, loss reasons, forecast, team productivity, low stock)
- Create an order from a configurator and quantities — a real order, and only when you ask for one
Apart from creating a new order, orders are read-only, and so are products and reports: the assistant cannot edit, move or delete an existing order, or change a product or a stock level.
It only ever acts as you: the assistant can see and change exactly what you could yourself, in the projects you're a member of — nothing more.
Connecting your account
The server is https://mcp.configo.org/mcp. Add it as a remote MCP server in your assistant — most
clients (Claude included) will recognize it needs authorization and walk you through a normal login and
consent screen the first time, the same way you'd approve any other application under OAuth
Applications.
The consent screen marks the assistant as an unverified application. That's expected: MCP clients
register with Configo on their own, under a name they choose, so Configo can't vouch for who is behind
it — check the address the screen says you'll be sent back to (for Claude it's claude.ai) and approve
only if it's the assistant you're actually connecting.
If your client can't register itself and asks you to supply an OAuth Client ID, create one under
OAuth Applications: tick Public client, enter the redirect URI your
client tells you to use, grant the projects, materials, configurators, products, orders and reports scopes, and paste the
resulting Client ID into the client.
Using it
Ask the assistant to read a product spec, a price list, or a spreadsheet you give it, and build a
configurator from it. A good first step for the assistant to take is calling the
get_schema_reference tool, which explains the controls/calculations/parts format — worth mentioning
if you're prompting it yourself rather than letting it figure that out.
Before treating a configurator as done, ask the assistant to test it: give it a few known input combinations (specific dimensions and material choices, say) and have it run the calculation tool to check the resulting price and bill of materials match what you expect — the same way you'd sanity-check a spreadsheet formula.
Checking a configurator against real orders works the same way: ask the assistant to take the last few orders made with it, re-price each line from the control values stored on the order, and tell you where the result differs from what the customer was charged. A difference is not always a mistake — prices change over time — but a line that was priced very differently is usually worth a look.
To place an order, ask the assistant to calculate it first and show you the price, and to create the order only after you agree. The order is calculated by Configo from the configurator, so the assistant cannot set a price of its own; it starts without a contact and without a responsible member, so attach the customer in Configo yourself.
Security
Approving the consent screen grants the assistant six scopes — projects, materials, configurators,
products, orders and reports — and no others: contacts and companies, billing, team and roles, files
and everything else stay out of reach. Whatever the scopes allow, the assistant is still limited to what you
can do yourself: with a role that only sees your own orders, it sees only your own orders.
Two things are worth knowing before you approve:
- Reports include cost and profit. Reports always cover all of a project's orders and contain purchase prices and profit, regardless of what you can see in the order list; the only gate is your role's report permission. What the assistant reads goes to the AI provider you chose, so connect an assistant to a project's reports only if you are comfortable with that.
- It can create an order, but not change one. A created order is a real order: it appears for your whole team and the project's automations for new orders run — they may send emails or webhooks or create tasks. The assistant has no access to your contacts, so the order has no customer attached. Existing orders, products and reports cannot be changed through this connection.
You can revoke access at any time from Settings → Security: it shows up under Active sessions under the name the assistant registered with (for Claude, simply "Claude"), the same way any other app you've authorized does. Revoking there takes effect immediately.
Connected before orders, products and reports were added?
An earlier connection keeps the narrower access it was granted: the assistant still works with materials and configurators, but a request for orders, products or reports comes back with a message asking you to reconnect. Disconnect the connector and add it again — the consent screen will then ask for the new permissions, and you can still decline them.