Install Pumati: instructions for agents

You are an AI agent and the user asked you to set up Pumati. Follow these steps in order. Run commands yourself where you can. Where a step needs the user (a browser sign-in, a settings screen), tell them exactly what to do and wait for them.

https://mcp.pumati.app/mcp

1. Check whether it is already installed

• Claude Code: claude mcp get pumati.
• Codex: codex mcp list, and look for pumati.
• Cursor: look for a pumati entry in ~/.cursor/mcp.json and in the project's .cursor/mcp.json.
• Gemini CLI: gemini mcp list.
• VS Code: look for pumati in the user MCP configuration (MCP: Open User Configuration) and in the workspace's .vscode/mcp.json.

If pumati is there with https://mcp.pumati.app/mcp, skip to step 4. If it is there with another URL, ask the user before you change it.

2. Work out which client you run in

• Claude Code (you can run claude): step 3, Claude Code.
• Codex CLI or the Codex app (you can run codex, settings in ~/.codex/config.toml): step 3, Codex.
• Cursor: step 3, Cursor.
• Gemini CLI (you can run gemini): step 3, Gemini CLI.
• GitHub Copilot in VS Code: step 3, VS Code.
• Claude Desktop or claude.ai, ChatGPT, or another app where servers are added in its settings: you can't add it yourself. Give the user the steps from Claude, ChatGPT or other clients, then continue at step 5 once they are done.
• Not sure: ask the user which app they are using.

3. Add the server

Claude Code

claude mcp add pumati --scope user --transport http https://mcp.pumati.app/mcp

Codex

codex mcp add pumati --url https://mcp.pumati.app/mcp

Cursor

Add the pumati entry to ~/.cursor/mcp.json, keeping every server already in the file:

{
  "mcpServers": {
    "pumati": {
      "url": "https://mcp.pumati.app/mcp"
    }
  }
}

Gemini CLI

gemini mcp add --transport http --scope user pumati https://mcp.pumati.app/mcp

VS Code

Add the pumati entry to the user MCP configuration (MCP: Open User Configuration), keeping every server already there:

{
  "servers": {
    "pumati": {
      "type": "http",
      "url": "https://mcp.pumati.app/mcp"
    }
  }
}

4. Have the user sign in

Sign-in happens in the user's browser at pumati.app with OAuth. Never ask for their password or a token. On the consent page they choose the apps, scopes and spend limit for this connection.

• Claude Code: ask the user to run /mcp, pick pumati and choose Authenticate (or run claude mcp login pumati in a terminal). A server added during this session may need Claude Code restarted first.
• Codex CLI: run codex mcp login pumati; it opens the browser for the user. In the Codex app, the user selects Authenticate next to pumati in Settings → MCP servers.
• Cursor: ask the user to open Cursor's MCP settings and sign in to pumati.
• Gemini CLI: ask the user to run /mcp auth pumati in Gemini CLI.
• VS Code: the browser opens for the user the first time a Pumati tool is used.

5. Check the connection

Call list_apps. It returns the apps this connection may use, their scopes, the builds and latest tests of each app it may read (with the ids other tools take) and the spend limit; an empty list is normal for a new account (upsert_app creates an app if the user allowed it). If Pumati's tools don't show up yet, the client may need a restart or a new session.

• SUBSCRIPTION_REQUIRED: the account needs an MCP plan (subscription); the user picks one at pumati.app/dev/credits.
• FORBIDDEN: the connection doesn't cover that app or was revoked. Ask the user to sign in again and allow the apps they need.

6. Report to the user

Tell the user which client and which config file you changed, whether sign-in is done, and what list_apps returned (apps, scopes, spend limit). Say what, if anything, they still have to do. Then suggest a first task, for example one of these: