Skip to main content
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

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 with your organization name to have it turned on.
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.
1

Add the Peeps server

Find your client below.
Claude Code registers itself with Peeps, so there is no client id to supply.
2

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.
3

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.
4

Know your invocation names

Plain English works everywhere — this is only for when you want to invoke a Peeps workflow directly.

​
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.
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.

What your agent can do

Four jobs, all in plain English.