PedibeeDocs

Connect an assistant

Add the Pedibee MCP server to Claude, ChatGPT, Claude Code, Cursor, VS Code or your own client, and approve it in Pedibee.

Connecting takes two steps: add the server in the assistant, then approve the connection in Pedibee. There is no key to copy; the assistant signs in through your browser.

Add the server in the assistant

The address is the same everywhere:

MCP server address
https://api.pedibee.com/mcp

On claude.ai or in Claude Desktop: Settings → Connectors → Add custom connector. Enter the address and click Connect.

Approve it in Pedibee

Pedibee opens in your browser. Sign in if needed and check what's asking: the page shows the app, its site and where you'll be sent back. Then choose:

  • The workspace the assistant may work in. One connection is one workspace; connect again for another.
  • What it can do. Start from Read only or Full access, or set each area: companies, contacts, lists, templates, campaigns, sequences, automations, events, Gmail and warm-up, and whether it may send email. You can't grant more than your own role allows.
  • Which Gmail, if sending is allowed: any connected Gmail or one Gmail only. That lock covers everything the assistant makes go out: one-off emails, campaigns, sequences, automations and warm-up.

Click Allow access and you're sent back to the assistant, connected.

Try it

"List my newest ten contacts." The assistant shows which tool it wants to run before it runs it. Then try "Show me the companies nobody has contacted in the last 30 days."

Managing connections

  • Settings → Connected apps lists every connection with what it may do and when it was last used. Everyone in the workspace can see the list; the owner and managers can disconnect, which stops it at once.
  • Connecting the same app to the same workspace again replaces the earlier connection.
  • A connection ends by itself when the person who approved it leaves the workspace, is removed, or becomes a member.
  • An assistant only ever sees the tools its access allows, and the server re-checks on every call.

API keys are for your own code

The MCP server only takes connections made this way. It refuses API keys. Use API keys for scripts and backends calling the REST API.

On this page