Skip to Content
LogoDevelopers
AI & AgentsAdmin AgentsInbound MCP Tools

Inbound MCP Tools

Inbound MCP tools connect an outside service to Finqu AI. The merchant registers an MCP  server on the Tools screen. When the connection is enabled, the Tools screen says it is available to workers and to the Success Agent.

That is separate from Admin MCP. Admin MCP lets an external agent operate Finqu. This page is the other direction: Finqu’s own assistant and workers call a server the merchant connected.

A playbook step asks for a title, a prompt, and a worker. That worker uses the tools checked on the worker screen.

Where merchants connect a server

Tools is in the admin, and Work Hub lists the same connections. Add opens the tool screen.

Connection

  • Name
  • Connection method. Streamable HTTP or SSE (Server-Sent Events). The hint says to leave the default unless the provider says otherwise.
  • Server URL. The hint says to paste the URL from the tool provider. It starts with https://.

Authentication

  • Type. No sign-in, API token, or OAuth 2.0 (connect by signing in).
  • For an API token, API token. The hint says to treat it like a password.
  • For OAuth, Sign in and connect opens the service’s sign-in window. The screen shows Connected or Not connected. Show advanced settings reveals Application ID (Client ID), Application secret (Client Secret), Sign-in URL (Authorization URL), Token URL, Requested permissions (scopes), and a Return URL (Redirect URI) to copy into the service’s OAuth app.

Settings

  • Enabled. The description says the tool is available to workers and to the Success Agent.

The side panel, What is this for?, says a connection expands what workers and the Success Agent can do.

What your server needs to offer

The merchant pastes your server’s URL and signs in the way your service requires. Your server is an MCP server:

  • Name each tool so a person can tell what it does, and describe when it should be used.
  • Say which inputs are required.
  • Return a clear result, or a clear error the assistant can show the merchant.
  • Finish quickly enough for a chat. For a long job, return a status the assistant can check later.

Where the tools show up

  • Success Agent. Merchants can turn a connected tool on or off for the chat. The assistant can ask before it uses a tool.
  • Workers. On the worker screen, check the tools that worker may use. Analyst, Planner, and Executor stay separate workers. A task starts from Work Hub, an automation, or a schedule.
  • Playbooks. Choose the worker on the step. The step’s prompt tells that worker what to do. Tools are the ones checked for that worker, including a connected server that is enabled.

Next steps

  • Workers — Check the tools a worker may use
  • Playbooks — A step picks a worker, not a tool list
  • Guidelines — Rules for how agents should behave
  • Admin MCP — Connect your own agent to Finqu