MCP Servers

Finqu provides Model Context Protocol (MCP) servers for connecting AI agents to merchant operations. Storefront agent access is provided through the Universal Commerce Protocol (UCP) — see Agentic Commerce for implementation guidance.

What is MCP?

Model Context Protocol (MCP) is an open protocol that enables AI agents to securely access external systems and tools. Finqu’s MCP servers act as bridges between agents and merchant operations.

Selecting the right MCP surface

Finqu exposes three distinct MCP surfaces depending on who is connecting and what systems they operate:

Surface	Direction	Who connects	Endpoint	What it does
Admin MCP	Outbound	External AI agents (Claude Desktop, Cursor, Codex, custom agent apps)	`https://mcp.finqu.com/mcp`	Direct merchant admin operations: catalog, orders, themes, content, and store configuration
MCP Tools	Inbound	Finqu AI (Success Agent, Workers, Playbooks)	External MCP servers you register	Bring your custom services, ERPs, and external APIs into Finqu admin automation
UCP MCP	Outbound	Customer-facing shopping agents	`{shop-domain}/mcp`	Storefront discovery, catalog browsing, cart management, and checkout flows

Admin MCP

The Admin MCP server gives any external AI agent direct, secure access to Finqu’s merchant operations. Whether you are running Claude Desktop, development agents in Cursor or Codex, or custom orchestration harnesses in TypeScript or Python, you can authenticate with standard OAuth 2.0 access tokens and execute admin tools over Streamable HTTP.

Admin MCP Overview — Architecture, endpoint, transport, and response envelopes
Connecting Agents — Setup recipes for Claude Desktop, Cursor, Codex, and official SDKs
Best Practices — Channel resolution, safety gates, confirmation flows, and error recovery
Authentication — OAuth discovery, token scopes, and permissions
Tools Catalog — Grouped reference of available Admin MCP tools

Storefront agent access via UCP

External agents that browse products, manage carts, and drive shopping flows connect through UCP, not Admin MCP. UCP exposes storefront capabilities via REST and MCP transports.

Agentic Commerce — Concepts, activation, and integration guide
UCP API Reference — Authentication, REST endpoints, MCP tools, and error codes
Activating UCP — Enable UCP on a sales channel

When UCP is enabled with the MCP server option, shopping agents connect at https://{shop-domain}/mcp using UCP tool names and metadata.

Next steps

Connecting Agents — Connect Claude Desktop, Cursor, or a custom agent
Admin MCP Best Practices — Operating rules and safety patterns for admin agents
Admin MCP Overview — Detailed server specifications and response models
Admin REST API — Same OAuth tokens over standard HTTP
UCP API Reference — Customer-facing agent integrations