Skip to main content
Connect a Model Context Protocol (MCP) server from Deploy → MCP servers. Workspace admins authorize access with the provider, browse its tools, and choose which tools to add as Actions for Rulebook.
Connecting a server does not import or run its tools. Use Add as Action for each tool you need, then configure its Rulebook inputs and any required confirmation before enabling writes. Read tools are imported as Actions too; this workflow does not automatically turn them into Attributes.

Before you start

You need a workspace admin account and a publicly reachable HTTPS MCP server that supports Streamable HTTP and OAuth discovery and registration. Use a server URL without embedded credentials, secret query parameters, or fragments. Sign in with the provider rather than pasting credentials into the URL. MCP connections must be enabled for your deployment. If connection management is unavailable, contact your Fini team. A merged feature or a visible Deploy card does not establish that the service is enabled.

Connect your MCP server

1

Open MCP servers

Open Deploy, find MCP servers under Internal Integrations, and click Configure.
2

Start authorization

Enter the MCP server URL and click Connect with OAuth. A Fini loading screen opens while the provider’s sign-in is prepared. Complete login and consent in that tab. If the tab does not open, use Continue to provider.
3

Check the saved connection

Return to Fini using the same account and workspace that started authorization. Connections update when you return; use Refresh connections if needed. Confirm the saved server is Connected before browsing tools.
4

Choose tools

In Saved servers, open the server card labeled Manage server. Its tools load automatically under Available tools when the connection is Connected. Review each tool’s description and input schema under Tool details, then click Add as Action for the tools you need. Added means the Action already exists; View Action opens it.

Use an imported Action

The MCP server defines the Action’s inputs. They are shown read-only in the Action editor; map the fields in your Rulebook rather than editing the server’s schema in Fini. Add the Action to the intended Tool node and place any required checks and confirmation before it. Imported Actions initially expose the tool response as a result output. Review the Action’s output fields to select the values your workflow needs. Fini uses structured tool content when supplied; otherwise it handles text or content blocks returned by the server. Do not assume that an MCP output schema automatically creates individual Attributes. Use Test Action with test inputs and test records before enabling the workflow. Inputs are validated against the imported tool schema before the MCP call. Testing can execute the tool: it is not a guaranteed dry run, and a write tool can change the connected system.
Use least-privilege provider access and import only the tools your workflows need. Configure write safeguards in Rulebook. Do not rely on tool annotations to create confirmation steps or on Fini to automatically inject an idempotency key; supply any required input explicitly through your workflow.

Update changed tool inputs

Open Manage server after changing a server’s tools. If the server is already open, click Refresh connections to reload its tools. When an imported tool’s input schema differs, its button changes to Update inputs. Review the new schema before updating, then check the affected Rulebook mappings and test the Action again. Updating inputs keeps the existing Action rather than creating a duplicate. New tools still need Add as Action. This workflow does not promise continuous schema sync, automatic output-field creation, or automatic repair of Rulebooks after a server change.

Manage a connection

Open Manage server from Saved servers to see connection controls and available tools. Use Back to servers to return to the cards or connect another server:

Why your MCP tools aren’t working

Confirm you are a workspace admin. If MCP connections are not enabled for your deployment, contact your Fini team.
Check the server URL and the provider’s OAuth discovery and registration support. Complete authorization in the account and workspace that started it. If authorization expired or was already used, reconnect to start again.
The connection must be Connected. Finish pending sign-in or reconnect, then refresh the connection list.
Connecting does not import tools. Open Manage server, confirm the server exposes the tool, and click Add as Action. If import rejects the input schema, check for unsupported schemas or unresolved references on the server.
Compare your Rulebook mappings with the tool’s required fields and types. Open Manage server and use Update inputs if the server changed its schema, then retest. Object and array inputs must contain valid JSON when supplied as text.
Check whether the server is disconnected or requires reconnection. Also confirm the tool still exists on the server and that the provider account has permission to run it. Review the Action result and test against safe records before retrying a write.