Peerbound is a platform that helps B2B marketing teams find customer proof in calls and reviews, turn it into customer stories, and deliver it to sales teams.
Agen.co connects to Peerbound through Peerbound's own hosted MCP server as an Official connector. Each user signs in with their own Peerbound account, so there is no app to register and no credentials to copy.
Prerequisites
Prerequisites
- A Peerbound account for each person whose agents will use the connector.
Peerbound registers Agen.co automatically, so there is no client ID or secret to copy and no callback URL to register.
In the Agen.co portal, go to Connectors → My connectors and click Add connector.
In the Select connector drawer, search for
Peerboundand select it. The Add Peerbound panel opens.Fill in the field:
Field Required Description Instance Slug Yes Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Prefilled withpeerbound. Use lowercase kebab-case. You can change it later from the connector's settings.Click Connect. Peerbound opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
On the Application Access Request page, check that the callback address under Credentials will be sent to is your Agen.co address, then click Allow Access. Complete the Peerbound sign-in if it asks for one.
Back in Agen.co, the panel switches to Select the tools to import from Peerbound. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even if the Peerbound tab reported success.
Peerbound does not publish documentation or a tool list for its MCP server, and the server only lists its tools after sign-in, so no tool table is given here. The tool selection screen that appears after Connect shows exactly what your account serves, and you can turn off any tool you do not want agents to use.
Enabling the Peerbound connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.