Skip to Content
AI CommerceMCP Tools

MCP Tools

MCP Tools let you connect any Model Context Protocol (MCP) server to Finqu. Once connected, the same tools are available to Workers and the Success Agent—so one integration powers both chat and background automation. As a partner or developer, you can plug in internal APIs, third-party services, or custom backends and have every agent use them consistently.

What you can build

  • Internal tools — Connect your own APIs (inventory, CRM, ERP, BI) so agents can read and act on data outside Finqu. Build support flows or automation that span multiple systems.
  • Third-party data and APIs — Weather, shipping, pricing, or content services exposed via MCP become available to the Success Agent and Workers without building separate integrations for each.
  • Custom APIs — Wrap your product’s API in an MCP server and offer it to merchants: the agent can then use your capabilities from the admin or from scheduled Workers.
  • Unified agent experience — One MCP server, one set of tools: the merchant chats with the Success Agent and triggers Workers; both use the same tools, so behavior and data stay consistent.

MCP Tools are shared across AI Commerce. Configure them once; they’re available to every Worker and the Success Agent that you enable them for.

Connection options

Finqu supports standard MCP connection patterns so you can integrate servers you already run or that third parties provide:

  • OAuth — For services that require user or app authorization. Configure OAuth so agents can access APIs on behalf of a merchant or your app.
  • Bearer tokens — For API keys or fixed tokens. Useful for internal or partner APIs where you manage credentials in the admin.
  • SSE (Server-Sent Events) — For streaming or long-lived MCP transports. Use when your MCP server uses SSE for tool calls or streaming responses.
  • Streamable HTTP — For HTTP-based MCP connections that support streaming. Lets you connect to MCP servers that speak HTTP with streaming semantics.

You choose the appropriate auth and transport when adding an MCP server in the admin. The same server can then be used by the Success Agent (for real-time chat) and by Workers (for scheduled or triggered runs).

How agents use MCP Tools

  • Success Agent — During a conversation, the agent can call tools from any connected MCP server (within the permissions you set). Merchants get a single assistant that can, for example, check inventory in your system and then update the store.
  • Workers — Executor, Planner, and Analyst can use the same tools. The Executor might call your API to sync data; the Analyst might pull external metrics; the Planner might use your recommendation service to suggest next steps.

Guidelines and tool permissions still apply: you control which tools are available to which agents and what they’re allowed to do. That keeps one integration flexible without giving every agent access to everything.

Combining with the rest of AI Commerce

  • Workers — Give Executor, Planner, and Analyst access to MCP Tools so they can read or write to your systems. Playbooks steps that assign tasks to Workers can use these tools when those steps are carried out.
  • Success Agent — Merchants get a chat experience that can invoke your tools (e.g. “Check stock in the warehouse”, “Create a ticket in our support system”).
  • Guidelines — Use Guidelines to describe when and how to use specific tools so agents don’t over- or misuse them.

For exposing the storefront to AI (e.g. shopping assistants, conversational storefronts), see Storefront MCP. For technical details on Finqu’s MCP servers and discovery, see MCP Servers.

Overview: AI Commerce → | Workers → | Success Agent → | Storefront MCP →