Admin AI & Automation

Finqu gives developers two ways to connect commerce automation, both built on the Model Context Protocol (MCP):

Drive Finqu with any agent. Connect an external agent, an IDE assistant (Cursor, Codex, Claude Desktop), or a custom agent to Finqu admin tools over Streamable HTTP.
Bring your own tools into Finqu AI. Connect an external API, ERP, CRM, or other service so the Success Agent and workers can use it.

Between those connections and the store’s own instructions, Work Hub is where merchants run Workers, Playbooks, and Events.

Two ways in

Where to go

Guide	Direction	What it is for
Admin MCP	Outbound	Connect Claude, Cursor, Codex, or a custom agent to catalog, orders, themes, and settings
Connecting Agents	Outbound	Configurations for those agents, in TypeScript and Python
Inbound MCP Tools	Inbound	Connect an outside MCP server on the Tools screen
Workers	In the admin	Analyst, Planner, and Executor. Each has instructions, tools, and a skill level. Any of the three can be started from Work Hub, an automation, or the calendar
Playbooks	In the admin	A name, a description, a status, and a linear list of steps. Each step has a title, a prompt, and a worker
Events	In the admin	Start a worker or a playbook from a store event or a schedule
Success Agent	In the admin	The merchant’s chat assistant
Guidelines	In the admin	Text rules aimed at workers, and at the Success Agent when that box is checked

In Work Hub

Success Agent. The chat in the admin. It answers questions and can carry out work the merchant allows, using Finqu and any tools the merchant has connected.
Workers. Separate helpers. Analyst, Planner, and Executor are chosen when the worker is created. A finished analyst task can be followed by Create a plan, and a finished planner task by Implement, when the merchant queues that follow-up.
Playbooks. A draft, active, or archived workflow whose steps are a numbered list. A run can start from the product list, from an automation, or from the calendar.
Automations. A store event or a schedule that starts one worker or one playbook.

Start here

Connect an external agent to Finqu. Follow Connecting Agents. Review Best Practices for the sales channel and for confirming changes.
Connect an external system into Finqu AI. Follow Inbound MCP Tools.
Automate a repeated job. Read Workers, then Playbooks, then Events.

Shopping agents

For a customer-facing assistant that browses products, manages a cart, and drives checkout, see Agentic Commerce. Storefront agent traffic uses the Universal Commerce Protocol (UCP), separate from Admin MCP.