The client connects to one endpoint
The MCP server URL is https://fivex.com/mcp/. The client uses your FiveX MCP key as a bearer token unless the client supports an OAuth flow.
MCP overview
How FiveX MCP tools work.
FiveX MCP gives AI clients a controlled set of tools for discovering connected channels, reading marketplace context and preparing approved actions.
Your AI client connects to the FiveX MCP server, authenticates with your FiveX key and then discovers what it can access based on the channels and permissions your team enables.
Discovery
Tool discovery starts from your FiveX setup.
After your AI client connects, it can ask the FiveX MCP server which tools and data surfaces are available for the current account.
FiveX returns available tools
The tools reflect the FiveX account, connected channels and access your team has enabled.
The agent adapts to the request
Instead of hard-coding every platform API, the agent can discover whether marketplace, advertising, inventory, product content or analytics context is available.
Access
Channel access stays explicit.
FiveX keeps connected channels disabled for AI access until your team enables them. This makes the MCP layer useful without making access invisible.
Amazon, bol, Kaufland and Otto
Use connected marketplace data for orders, products, stock, margins and performance questions.
Google Ads, Meta Ads and retail media
Let AI review campaign performance while keeping channel access controlled in FiveX.
Shopify and ecommerce systems
Connect storefront context to marketplace and advertising workflows.
Reporting and warehouse datasets
Use API and export patterns when workflows need historical or warehouse-scale analysis.
Workflows
Start read-first, then move to approved actions.
MCP works best when teams begin with safe analysis and move toward operational actions only after the tool behavior is understood.
Read workflows
Ask for available tools, retrieve account context, inspect channel performance or summarize stock and advertising risks.
Decision workflows
Ask the agent to identify products, campaigns or channels that need review, then explain the reasoning before any action.
Approved action workflows
Only let the agent prepare or execute changes after a user explicitly approves the exact action and channel scope.
Manual setup
Manual configuration is available when the client needs it.
Some MCP clients can add servers from a command line. Others need manual configuration in settings.
Command-line clients
Use the client's MCP add command with http transport and the FiveX MCP server URL.
Manual clients
Add the server URL and configure the Authorization bearer header with your FiveX MCP key.
Verification
Ask the client what FiveX tools and connected channels are available before asking operational questions.
Next steps
Continue with setup and governance.
Use the quickstart to connect a client, then review security, connectors and SDK patterns for production workflows.
Quickstart
Connect your AI client
Follow the guided setup for keys, client connection and verification.
Open SecurityReview tokens and governance
Keep credentials private and pair MCP access with explicit channel permissions.
Open ConnectorsChoose channel coverage
Map marketplaces, ads, commerce systems and warehouse data to the workflows AI may use.
Open SDKOpen setup in an agent
Use the SDK page to open the FiveX MCP setup prompt in Codex, Claude Code, Cursor, Copilot and more.
OpenReady to test FiveX MCP tools?
Connect your client, ask what tools are available and start with read-only marketplace questions.