Connect external tools through MCP
Control MCP provides a standard interface for compatible AI clients, automation platforms, and custom tools to work with financial context from Control. Use it when an external workflow needs governed access to the same data your finance team reviews.Read and write access
Treat read and write capabilities as separate decisions:
Write-capable MCP actions are controlled separately from read access. Available write operations are limited to an explicit allowlist rather than granting broad modification rights.
Control binds MCP requests to the connected workspace and blocks write tools in read-only sessions. The generic request tool does not add a separate entity-level scope beyond the access enforced by the underlying Control endpoint. Write activity produces structured operational logs, not a durable user-visible audit record, so keep an approval and audit trail in the workflow that invokes MCP.
Start with read-only access unless the external workflow has a reviewed need to write. Enable only the specific write operations required by that workflow.
Before you connect a tool
- Identify the user and business process that owns the connection.
- Define the financial scope the tool needs.
- Decide whether read-only access is sufficient.
- Review how the external client stores credentials and conversation data.
- Establish how your team will review activity produced by the connection.
Set up MCP access
Use the MCP onboarding flow in the Data Outputs area to create the connection information required by your client. Complete the client-specific setup using the instructions shown by Control and the external tool. After connecting, begin with a narrow, verifiable request—for example, retrieving a known actual value for one period and entity. Compare the response with the corresponding view in Control before expanding the workflow.Design a safe workflow
- Request the smallest necessary scope.
- Keep write access disabled when the workflow only needs analysis.
- Require a human review before consequential financial changes.
- Validate generated analysis against statements and supporting transactions.
- Remove or rotate access when the owning user, client, or business purpose changes.
Verify the connection
- Confirm that the client can connect without exposing its credentials.
- Run a read-only request for a known entity, period, and metric.
- Reconcile the response with Control.
- Confirm that a read-only session rejects write tools and returns data only from the expected workspace.
- If write access is enabled, test only an approved low-risk operation, record the request and result in your workflow’s audit trail, and confirm the resulting change in Control.