MCP
#MCP Capabilities
When you interact with the Akeneo MCP Server through natural language (for example with Claude, Cursor, or VS Code), your AI assistant automatically calls MCP Tools behind the scenes.
These tools represent the "capabilities" of the Akeneo MCP Server — for instance:
get_products- Retrieve one or multiple productsget_families- List product familiesget_attributes- List attributes with filtering optionsupsert_products- Update or create several products- And more...
Your LLM interprets your intent (e.g. "Show me all disabled products") and dynamically selects and fills the right tool parameters (e.g. calling get_products with enabled=false).
#List & Debug The MCP Capabilities
If you want to see, explore, or debug these tools directly, there are a few options:
#MCP Inspector
MCP Inspector is an open-source web app created by the Model Context Protocol team. It lets you connect to any MCP server, visualize its declared tools, schemas, prompts, and resources, and even manually trigger tool calls.
How to use it:
- Go to MCP Inspector
- Connect to the Akeneo MCP Server at
https://server.mcp.akeneo.cloud/mcp - Add your Akeneo credentials as headers:
X-Akeneo-API-URL: Your PIM URLX-Akeneo-Client-ID: Your client IDX-Akeneo-Client-Secret: Your client secretX-Akeneo-Username: Your usernameX-Akeneo-Password: Your password
- Browse available tools and test them directly
#Postman
Postman now includes built-in support for MCP requests. You can directly query an MCP server, list its tools, and call them using the Postman interface.
How to use it:
- In Postman, create a new "MCP" Collection
- Set the server URL to
https://server.mcp.akeneo.cloud/mcp - Add headers (optional if you just want to list the tools):
X-Akeneo-API-URL: "https://your-pim.akeneo.com" X-Akeneo-Client-ID: "your_client_id" X-Akeneo-Client-Secret: "your_client_secret" X-Akeneo-Username: "your_username" X-Akeneo-Password: "your_password" - Click "Run" to see the full list of capabilities
- Select a tool (e.g.
get_products) and test it directly
#Understanding Tool Responses
When you call MCP tools directly, the response is wrapped in a standard MCP structure:
- structuredContent: Structured JSON payload with tool-specific data
- Example for
get_products: aproductobject andendpoint_used - For search tools, you may also see
parameters_used
- Example for
- content[]: Raw, textual representation of the same data (for LLM rendering)
- isError: Boolean indicating whether the tool call failed
This mirrors what your LLM receives when handling your request, providing full visibility into the MCP server behavior.
#Learn More
- Model Context Protocol: modelcontextprotocol.io
- Understand MCP Servers and Clients
- MCP Server concepts