MCP tools

FiveX MCP tools and capabilities

After an MCP-compatible client authenticates to FiveX MCP, it discovers the tools available for the current account based on enabled channels and permissions.

Exact tool names are returned by the MCP server for your workspace. This page documents the capability domains FiveX MCP can expose, the read/write model and example prompts. Do not assume every account has the same write tools.

Start quickstart Permissions

Discovery

How tools are discovered

FiveX MCP does not require you to hard-code a static public tool list into every client. The client asks the server which tools are available after authentication.

Connect to the endpoint

Use https://fivex.com/mcp/ with Authorization: Bearer <FIVEX_MCP_KEY>, or follow an OAuth flow when the client supports it.

Ask the server for tools

Have the client retrieve available tools for the authenticated FiveX account.

Verify channel access

Ask which connected channels and commerce data surfaces are available before running operational requests.

What FiveX tools and connected channels do you have available?

Capability model

Read, analyze, recommend, act, approve

Use this model to understand what FiveX MCP can support without overstating autonomous write access.

Read

Retrieve and inspect commerce information through available MCP tools.

Analyze

Combine returned data so the AI client can explain performance and changes.

Recommend

Use retrieved context to suggest next actions. Recommendations are not executions.

Act

Execute supported actions only when the relevant tools are exposed and permissions allow them.

Approve

Require human confirmation for operational changes before they are applied.

Capability matrix

Commerce capability domains

These domains describe commerce context FiveX can expose through MCP when channels and permissions are enabled. Act support is permissioned and account-specific.

Capability Read Analyze Recommend Act Example channels
Orders Yes Yes Yes — Amazon, bol, Kaufland, Otto, Shopify
Sales & performance Yes Yes Yes — Amazon, bol, Kaufland, Otto, Shopify
Inventory Yes Yes Yes Permissioned Amazon, bol, Kaufland, Otto, Shopify
Advertising Yes Yes Yes Permissioned Google Ads, Meta Ads, Amazon Advertising
Pricing Yes Yes Yes Permissioned Amazon, bol, Kaufland, Otto
Listings & product content Yes Yes Yes Permissioned Amazon, bol, Kaufland, Otto, Shopify
Products & assortment Yes Yes Yes — Amazon, bol, Kaufland, Otto, Shopify
Profitability Yes Yes Yes — Amazon, bol, Kaufland, Otto, Shopify
Returns Yes Yes Yes — Amazon, bol, Kaufland, Otto

Act = permissioned means a write or operational tool may exist only when enabled for the account. It does not mean every listed channel currently exposes a write action through MCP.

Example prompts

Prompts that use cross-channel commerce context

These prompts demonstrate FiveX strengths when the relevant data surfaces are available. They do not invent tools that your account may not expose.

  • Which products have high advertising spend but low contribution margin?
  • Which products have active advertising but less than 14 days of inventory?
  • Compare profitability for the same products across Amazon and bol.
  • Which channels require my attention today?
  • Why did Amazon profit decline last week?
  • What are the five most important things I should review today?

Multi-step workflows

How agents combine multiple MCP tools

An AI agent can call multiple FiveX MCP tools to answer a complex question. FiveX returns commerce context. The AI client performs the reasoning.

Find products with declining profitability and tell me why.
  1. Retrieve product performance context.
  2. Identify profitability decline.
  3. Retrieve advertising performance where available.
  4. Retrieve inventory context where available.
  5. Retrieve relevant pricing or channel information.
  6. The AI client analyzes the returned context.
  7. The AI client explains likely causes and recommends next actions.
  8. Supported actions may be executed only after permission and approval.

Next steps

Continue with permissions, setup and use cases

Security

Permissions and security

Authentication, channel permissions, approvals and governance.

Open Setup

Quickstart

Connect an MCP client and verify tool discovery.

Open Examples

Use cases

Practical commerce questions organized by category.

Open API

Security governance

Token handling and API security guidance.

Open

Discover the tools available for your account.

Connect your MCP client, ask which tools are available, then start with read-only commerce questions.

Start quickstart Open permissions