> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cfo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent instructions

> Help a user connect the cfo.ai MCP server, complete browser-based authentication, select the correct workspace, and work safely.

You are helping a user connect cfo.ai to an external AI client. The cfo.ai MCP server exposes the same workspace tools Ari uses, including tools that can read and change a live financial Model.

You can configure the MCP client. The user completes account creation, sign-in, any required plan setup, and browser-based authorization. A connection is complete only when the client lists the server and can use an authorized cfo.ai tool.

## Confirm account access

Ask whether the user can already sign in to [app.cfo.ai](https://app.cfo.ai). If they cannot, direct them to create or access their account and complete any required setup in the browser.

Wait for the user to finish browser-only steps. Never ask for their password, verification code, payment details, or authorization token.

## Register the MCP server

The production server URL is:

```text theme={null}
https://api.cfo.ai/mcp
```

For Claude Code:

```bash theme={null}
claude mcp add --transport http cfoai https://api.cfo.ai/mcp
```

For Codex:

```bash theme={null}
codex mcp add cfoai --url https://api.cfo.ai/mcp
```

For another client, add `https://api.cfo.ai/mcp` as a remote HTTP MCP server named `cfoai`.

If you cannot execute a setup command, give the matching command to the user and wait for them to complete it.

## Complete browser authentication

The user approves the connection in a browser while signed in to cfo.ai.

* In Claude Code, restart the session if needed, open `/mcp`, select `cfoai`, and choose **Authenticate**.
* In Codex, run `codex mcp login cfoai` and approve the connection in the browser.
* In another client, follow its normal OAuth or remote-MCP authorization flow.

## Verify the connection and workspace

Confirm that the client lists `cfoai` and exposes its tools. A user with one workspace can usually use that workspace automatically. If the user has access to more than one workspace, call `list_orgs` and pass the intended workspace's ID or slug as `org_id` on subsequent calls.

Use a read-only inspection call to verify access before reporting success. If the client does not see the newly registered server, restart the session and check its MCP server list again.

## Understand the Model before changing it

The MCP connection provides cfo.ai's modeling instructions during initialization. When the connected client exposes `inspect_reference`, use it to read the relevant product guidance. Use the available `inspect_variables`, `inspect_dimensions`, and `inspect_table_blocks` tools to understand the existing workspace before creating or changing content.

The important mental model is:

* A workspace contains a financial Model, Pages, Scenarios, Variables, Dimensions, and connected data.
* Main is the primary working Scenario. Use a different Scenario when the user wants a saved alternative.
* `inspect_variables`, `inspect_dimensions`, and `inspect_table_blocks` read the existing Model.
* `edit_table_blocks` changes visible saved tables and their formulas.
* `edit_variables` changes Variable definitions or genuinely table-independent formulas.
* Write operations apply to the user's live Model and must match the user's request and workspace access.

## Troubleshoot access

* If `cfoai` is missing, restart the client and check whether the server registration succeeded.
* If browser authentication fails, confirm that the user is signed in to the intended cfo.ai account and has access to the intended workspace.
* If tools report authorization errors after a previous success, repeat the client's authentication flow.
* If a workspace is ambiguous, call `list_orgs` and pass the intended workspace as `org_id`.