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

# Connect your agent to Peeps

> Connect Claude Code, Cursor, or Codex to the Peeps MCP server. One command per client, approved once in your browser.

Connect your agent to Peeps once per machine, in whichever client you use. The connection is not per-repo, so run it from anywhere.

## First: get your organization enabled

<Warning>
  **MCP is off by default for every organization.** Nothing below will work until it is switched on, and only Peeps staff can do it — an org admin cannot self-enable.

  Email [support@peepsai.com](mailto:support@peepsai.com) with your organization name to have it turned on.
</Warning>

This is deliberate. MCP hands an external coding agent read access to your organization's failure evidence, so turning it on is a decision we make with you rather than a toggle.

Once it is on, everything below takes about two minutes.

<Steps>
  <Step title="Add the Peeps server">
    Find your client below.

    <Tabs>
      <Tab title="Claude Code">
        ```bash theme={null}
        claude mcp add --transport http peeps https://app.peepsai.com/api/mcp
        ```

        Claude Code registers itself with Peeps, so there is no client id to supply.
      </Tab>

      <Tab title="Cursor">
        Add Peeps to `~/.cursor/mcp.json`, then approve the sign-in when Cursor prompts.

        ```json ~/.cursor/mcp.json theme={null}
        {
          "mcpServers": {
            "peeps": {
              "url": "https://app.peepsai.com/api/mcp",
              "auth": {
                "CLIENT_ID": "peeps-cursor",
                "scopes": ["read", "run", "edit", "publish", "offline_access"]
              }
            }
          }
        }
        ```

        <Warning>
          The `auth` block is required. Without `CLIENT_ID`, Cursor falls back to registering itself, which Peeps cannot accept — the server would install but never authorize.
        </Warning>

        Verified against Cursor IDE `3.15.19` and Agent CLI `2026.08.11`.
      </Tab>

      <Tab title="Codex">
        Two commands. Add the server, then sign in.

        ```bash theme={null}
        codex mcp add peeps --url https://app.peepsai.com/api/mcp --oauth-client-id peeps-codex
        ```

        ```bash theme={null}
        codex mcp login peeps
        ```

        The login command opens the browser approval. No other flags are needed — there is no `--transport` flag on `codex mcp add`.

        Verified against Codex CLI `0.147.0`.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Approve the connection">
    The first time your agent reaches Peeps, you are sent to your browser to sign in and approve access. The consent screen names exactly what this client is being granted.

    Approve it, return to your editor, and the connection stays authorised.
  </Step>

  <Step title="Check that it works">
    In any of the three clients, ask your agent:

    > Who am I in Peeps?

    It should list your organizations, your role in each, and whether MCP is enabled for them. If you see them, you are connected.
  </Step>

  <Step title="Know your invocation names">
    Plain English works everywhere — this is only for when you want to invoke a Peeps workflow directly.

    | Client      | Troubleshooting       | Coverage       |
    | ----------- | --------------------- | -------------- |
    | Claude Code | `/peeps:troubleshoot` | `/peeps:cover` |
    | Cursor      | `/peeps-troubleshoot` | `/peeps-cover` |
    | Codex       | `peeps-troubleshoot`  | `$peeps-cover` |
  </Step>
</Steps>

## Managing the connection

Peeps settings, under **Coding agents**, lists every client you have authorized and lets you revoke one. Reconnect from the same page if a tool ever reports insufficient scope.

<Warning>
  Revoking stops a client renewing its access. It does not kill a token already in that client's hands — an access token stays valid until it expires, up to 15 minutes later.

  Revoking also applies to every installation authorized under that client, on every machine, not just this one.
</Warning>

<Card title="What your agent can do" icon="arrow-right" horizontal href="/capabilities">
  Four jobs, all in plain English.
</Card>