Skip to main content
Use these checks when an MCP client cannot connect to Control, shows the wrong workspace, or cannot retrieve the financial data you expect.

​
Availability

Control MCP requires a Control account, access to at least one Control workspace, and a compatible MCP client. Marketplace installation is available only in clients where Control appears in the public connector directory. If Control is not listed, connect with the workspace-specific server URL shown in Control.

​
Quick checks

  1. Copy the current server URL from Data outputs → MCP Server in Control.
  2. Confirm that you can open the intended workspace in Control with the same user account.
  3. Ask the client to refresh its MCP tools or reconnect the server.
  4. Check that the workspace’s accounting source has finished synchronizing.

​
Causes and resolutions

​
Sign-in or authorization does not finish

How to confirm: The browser does not return to the MCP client, or the client still shows Control as disconnected after authorization. Resolution:
  1. Return to the MCP client and restart the connection.
  2. Allow the authorization window and redirects for the MCP client and Control.
  3. Sign in with a user who can open the intended Control workspace.
  4. If the authorization request expired, start a new request instead of reusing the old URL.
Verify: Control appears as connected and the client can refresh its MCP tool list.

​
The wrong workspace is connected

How to confirm: The client returns entities or financial statements from a different Control workspace than you expected. Resolution:
  • For a manually configured connection, remove it and copy the workspace-specific server URL again from Data outputs → MCP Server in the intended workspace.
  • For a marketplace connection, when available, disconnect Control and select the intended workspace when you authorize it again.
Do not add or change workspace identifiers in prompts, headers, or a marketplace MCP URL. Verify: Ask the client to list the available entities and confirm that they belong to the intended workspace.

​
The client shows no tools or an old tool list

How to confirm: Control is connected, but expected MCP tools are missing or the client shows an outdated catalog. Resolution: Ask the client to refresh its MCP tools. If that does not work, disconnect and reconnect Control. Verify: The client’s refreshed tool list matches the access available to your Control user and workspace.

​
No financial data is available

How to confirm: The connection succeeds, but requests return no entities, statements, or actuals. Resolution:
  1. Open the intended workspace in Control.
  2. Confirm that an accounting source is connected.
  3. Wait for its initial synchronization to finish before retrying the request.
Enter accounting credentials only in Control’s integration flow. Never put them in an MCP prompt, tool argument, or support request. Verify: Compare a narrow request for a known entity, period, and metric with the corresponding view in Control.

​
Accounting data is stale or synchronization failed

How to confirm: Control shows an integration error or a last synchronization time older than the data you expect. Resolution: Open the affected accounting integration in Control, resolve the displayed connection or synchronization error, and wait for the next successful synchronization. Verify: Confirm the updated synchronization time in Control, then retry the same MCP request.

​
A requested action is unavailable

How to confirm: The client cannot find a tool for the requested action or reports that the operation is not permitted. Resolution: Refresh the tool list and check the user’s Control permissions. Marketplace connections, when available, begin with a limited read-only tool catalog. Use Control directly for actions that are not exposed to the current MCP connection. Verify: Run a read-only request supported by one of the tools returned by tools/list.

​
Disconnect or change access

Remove Control from the MCP client’s connector settings. Reconnect and authorize again if you need to use a different workspace or access level. Menu labels vary by client. If the client still accesses Control after you remove the connection, contact support with the safe diagnostic information below.

​
Collect information for support

Email hello@control.dev with:
  • the MCP client and whether you used a server URL or marketplace listing;
  • the approximate time of the problem and your timezone;
  • the step that failed and what you expected to happen; and
  • the exact error text after removing financial data, personal data, and secrets.
Never send access tokens, refresh tokens, authorization codes, PKCE values, passwords, accounting credentials, financial exports, or unredacted screenshots. Control support will provide a safer diagnostic path if more detail is required.
For security and privacy information, see the Control Trust Center and Privacy Policy.

​
Related content