Access the MCP server
Private beta: access through the IAMP platform only
The Quable MCP server is a private beta. It is not a public API.
- Access is only authorized through the IAMP platform. Connecting to the MCP server from any other client (Claude Desktop, Cursor, VS Code, custom scripts, etc.) is not authorized.
- Any tool, prompt, resource, parameter or behavior can change or be removed at any time, without notice. Do not build integrations that depend on it.
Prerequisites
To use the MCP server from the IAMP platform, you need:
Instance name format
The instance name contains only lowercase letters a-z and hyphens -. Any other character is rejected with an Invalid instance format error.
Read or full access?
With a Read access token, the assistant can explore your data but every write tool fails. Use a Full access token only if you want the assistant to modify data.
How authentication works
The IAMP platform sends your instance name and token with every request to the MCP server, in the X-Quable-Instance and Authorization: Bearer <token> headers. The MCP server validates the token against your instance before running any tool, and every tool then acts with the rights of that token.
Keep your token secret
The token gives access to your catalog. Use a dedicated token for AI use, so you can revoke it without impacting your other integrations.
Check the connection
Ask your assistant:
Call test_credentials on the Quable MCP server.
The expected answer is {"status": "valid credential"}. If you get an error, see Troubleshooting.
Start a session
Before working on your data, ask the assistant to load the PIM structure with the pim-bootstrap prompt:
Get the pim-bootstrap prompt from the Quable server and follow its instructions.
The assistant then reads your user profile, active locales, document types, link types and completeness rules. From there it uses your exact codes (fr_FR, reference_color…) instead of guessing them from labels. See Workflows.