MCP Server

Connect Estii to Claude Code, Codex, Cursor, or any other AI agent, so it can read and update your deals in plain language. Setup is one line, with nothing to install.

Set it up

The quickest path needs only Node. npx fetches and runs the server, so there is nothing to install first.

Claude Code

claude mcp add estii -- npx -y @estii.com/cli mcp serve

Then open /mcp in Claude Code to confirm estii is connected.

Codex

Add a block to ~/.codex/config.toml:

[mcp_servers.estii]
command = "npx"
args = ["-y", "@estii.com/cli", "mcp", "serve"]

Other clients

Any MCP client works. Point its command at npx with args -y @estii.com/cli mcp serve. If you have the CLI installed, point it at estii with args mcp serve instead.

Sign in

The server uses your Estii identity, so signing in once is enough:

npx @estii.com/cli auth login

For headless or shared setups, pass a token in the server's environment instead of signing in. In Claude Code:

claude mcp add estii --env ESTII_TOKEN=estp_your_token -- npx -y @estii.com/cli mcp serve

In Codex, add an [mcp_servers.estii.env] block that sets ESTII_TOKEN. See API keys to create a token. Browsing works with no credential; reading and updating your deals needs one.

After you change the server (new token, new version), restart the connection: toggle estii off and on in your client, or restart it.

Talk to your agent

Once connected, just ask in plain language. Talk in names, not ids, and the agent looks things up. Not sure where to start? Ask it what it can do:

What can you do with my Estii deals?

Show me the deals in Acme Consulting.

Summarise the ACME Customer Portal deal, with margin and phases.

What would a senior engineer for 10 days cost in this space?

Export the ACME Customer Portal deal to xlsx and give me the link.

Set the target price on ACME Customer Portal to 300k.

Request approval for the ACME Customer Portal deal.

Reads are safe and changes are explicit: the agent confirms before it writes anything, and you can ask for a dry run to preview a change first.

How it works

estii mcp serve runs the CLI as a Model Context Protocol server over stdio, speaking the same API contract as everything else. The agent gets three tools:

• command reference — the full command catalogue, so the agent learns what it can do. No sign-in needed.
• read — anything read-only: list, show, export, estimate.
• change — anything that writes: set a field, or a lifecycle event (request approval, approve, close).

You never name the tools yourself; the agent picks the right one. Read and change together cover the CLI's entire surface (the same catalogue as estii commands), which is why asking the agent what it can do just works.

Learn more