sellbird
4.6kRequest early access

Your agent. Connected.

Set up Sellbird’s remote MCP connection, select a workspace, prepare outreach and handle replies, with clear approval boundaries and troubleshooting steps.

Request early access Read as Markdown

What the connection does

MCP (Model Context Protocol) lets your AI client discover and call Sellbird tools. Your agent researches buyers with its own sources and writes the messages. Sellbird stores contacts and campaigns, schedules sending, and collects replies. Connecting MCP does not give Sellbird a model of its own or keep your agent thinking between sessions.

Sellbird works with any client that supports remote MCP with OAuth sign-in, such as Claude, Claude Code, ChatGPT, Codex and Cursor. Copy the MCP address from the Agents page in your account and add it to your client. Support depends on the client’s version, plan and admin settings.

Sellbird has no AI of its own and doesn’t charge for it. Your agent runs on the AI plan or API you already pay for.

Connect your agent

You need a hosted Sellbird account, access to the workspace you want to use, and an AI client that supports remote MCP over HTTP with OAuth. A provider login on this website signs you into Sellbird; it is separate from granting your agent MCP access or connecting a sending mailbox.

  1. Sign in to Sellbird and open Agents. Copy the MCP address shown there. Use that address rather than a guessed marketing-site URL.
  2. Add that address as a remote MCP server or custom connector in your AI client. Follow the client’s connection instructions; menu names and plan requirements differ.
  3. Complete the browser sign-in and authorisation flow. Return to the client and confirm that Sellbird tools are available. Do not paste your email password or a hosting secret into the conversation.
  4. Ask your agent to list the workspaces it can access, select the intended workspace and read setup status before making changes.

Your first outreach session

Start with a small, specific audience and tell your agent what you sell, which sources it may use and what a qualified buyer looks like. Company facts and contact details should have evidence; the illustration data on this website is fictional.

  1. Ask what needs attention and whether sending is paused. Resolve any setup requirements in the dashboard.
  2. Research prospects with your agent’s own tools, then import contacts and supporting context. An imported email is not automatically verified.
  3. Create a campaign and prepare personalised drafts. Review recipients, claims, links and follow-up timing in the Outbox.
  4. Approve the work you want to send. Sellbird applies sending limits, suppression rules and scheduling; approval is not a guarantee of delivery.
  5. On the next session, ask for replies that need an answer. Have your agent prepare responses, then review those drafts in the Outbox.

Try this prompt:

Show me what needs attention in my workspace. Check setup and sending status. Research ten Austin roofing companies that book inspections by phone, keep the sources for each finding, and prepare introductions for review. Do not enable autopilot or approve purchases.

Useful tools to ask your agent about

The connected server supplies the current tool definitions and argument schemas. These are examples of the workflow, not a replacement for that live reference. Some tools or setup operations depend on your account and deployment.

  • attention, setup_status and sending_status: check work awaiting you, setup progress and whether sending is paused.
  • workspaces_list and workspaces_set_default: inspect accessible hosted workspaces and choose the default. Pass workspace explicitly when work spans clients.
  • contacts_import, prospects_list and cohort_preview: bring in contacts, inspect them and preview audiences from their signals.
  • campaigns_create, campaigns_add_prospects and outbox_edit_draft: prepare campaigns and drafts for the sending workflow.
  • replies_list and replies_draft: inspect conversations needing attention and prepare a reply for review.
  • sending_pause and suppressions_add: stop sending or prevent further outreach to a recipient. An agent cannot resume sending.

Approval, access and agent sessions

Every campaign email waits for your approval by default. A workspace owner can turn on autopilot in settings, and then campaign emails send without one-by-one approval, still inside your sending limits and opt-out rules. Reply drafts always need your approval. Your agent can never turn on autopilot, approve a draft or approve a purchase.

A hosted connection acts within the signed-in user’s workspace access. Selecting a default workspace routes requests; it does not create a security boundary that blocks that user’s other authorised workspaces. For client work, verify the workspace on every write and grant team members only the access they need.

An agent can read contact and conversation content through tools. That content may be processed by the AI provider you choose under its own terms. Review your provider’s data settings before connecting sensitive customer information.

Scheduled, approved work and reply collection continue between agent sessions. Research and new reply drafting need your agent to run again; MCP by itself is not a background agent scheduler.

Troubleshooting and disconnecting

  • No tools appear: confirm the copied MCP address, remote HTTP and OAuth support, and any administrator restrictions in the client. Complete authorisation before retrying.
  • Wrong workspace or access denied: ask for accessible workspaces, select the intended one and confirm your membership. Do not assume a default selection grants additional access.
  • A draft did not send: inspect its approval state, recipient verification, suppressions, sending hours, daily limits and mailbox health. Do not work around a paused or blocked send.
  • A repeated write times out: inspect the result before retrying. When a tool accepts an idempotency key, reuse the same key for the same operation to avoid duplicate work.
  • Disconnect an agent on the Agents page, or pause agent access for a workspace. Disconnecting MCP does not cancel already queued mail: pause sending separately if you also want the queue stopped.

Hosted and self-hosted MCP

Hosted Sellbird exposes a remote, authenticated endpoint. Self-hosted Sellbird can run locally and has its own installation and discovery setup. Use the current installation instructions in the public repository for the version you run; do not copy a hosted MCP address into a local-only setup.

The shared workflow does not mean every tool is interchangeable. Hosted buyer research is performed by your connected agent and its tools, while self-hosted discovery has its own configured sources.

Keep exploring