Connect an AI Assistant via MCP

How to get there: There is nothing to switch on in Boei. Open the AI tool you use and add Boei as a connector using the address below. Boei asks you to sign in and approve the connection. This page has steps for Claude, Claude Desktop, ChatGPT, Codex, Claude Code, Cursor, VS Code, Gemini CLI, Windsurf, Zed, Cline, and Goose.

Boei works as an MCP server. MCP (Model Context Protocol) is the standard AI assistants use to work with other apps. Once connected, your assistant can look up contacts, update deals, read and reply in your inbox, edit FAQs, and add training content to your chatbots, all inside your normal chat with the assistant.

Everything the assistant does happens as you. It can only see and change what your own Boei login can see and change.

Which plans include it

MCP uses the same access as the Boei API. It is included on plans with API access and during your free trial. If your plan does not include API access, the connection is refused with an "upgrade" message.

The address to connect

https://app.boei.help/mcp

That is the only thing you need to paste. Your AI tool finds the sign-in screen on its own.

Pick your tool:

Your tool has to be able to open the Boei sign-in screen in a browser. Tools that only let you paste a key, such as GitHub Copilot CLI at the moment, cannot connect to Boei yet.

Connect from Claude

  1. In Claude, open Settings and then Connectors.
  2. Click Add custom connector.
  3. Give it a name, for example "Boei", and paste https://app.boei.help/mcp as the URL.
  4. Two groups of settings appear, Authentication and OAuth client. Claude checks our server and fills both in for you, marking its choices Detected. Leave them exactly as they are. You do not need to add any headers or open the Advanced section.
  5. Click Add.
  6. Open the connector you just added and click Connect. A Boei window opens.
  7. Sign in with your normal Boei email and password if asked.
  8. Check what the assistant will be allowed to do and click Allow.

Claude now lists every Boei action it can take. In the connector settings you can decide which actions run automatically and which ones ask you first. We recommend leaving delete actions on "ask first".

Connect from Claude Desktop

Claude Desktop has the same Settings → Connectors screen as Claude on the web. Follow the steps above. The sign-in opens in a separate window; once you click Allow, the connection stays in place when you restart the app.

Connect from ChatGPT

ChatGPT calls this a custom connector. It needs Developer mode, which is available on the Plus, Pro, Business, Enterprise, and Edu plans. If your company manages your ChatGPT workspace, an admin has to allow custom connectors first.

  1. Open Settings, then Security and login, and switch on Developer mode. In older versions of ChatGPT this switch is under Settings → Apps → Advanced settings.
  2. Open Settings, then Connectors, and click Create. Newer versions call this page Plugins and show a plus button instead.
  3. Give it a name, for example "Boei", and a one-line description such as "Manage my Boei contacts, deals, inbox, and chatbot training". ChatGPT reads the description to decide when to use the connector.
  4. Paste https://app.boei.help/mcp as the server address and choose OAuth as the authentication.
  5. Click Create. A Boei window opens. Sign in if asked and click Allow.

In a conversation, open the plus menu and switch the Boei connector on before you ask it something.

Connect from Codex

Codex is OpenAI's coding assistant. It comes as part of the ChatGPT desktop app, as a command-line tool, and as an editor extension. All three share one setup, so you only do this once.

In the ChatGPT desktop app or the Codex editor extension:

  1. Open Settings (in the editor extension: the gear icon) and choose MCP servers.
  2. Click Add server.
  3. Choose Streamable HTTP, name it boei, and paste https://app.boei.help/mcp.
  4. Click Save, then Restart.
  5. A Boei window opens. Sign in if asked and click Allow. If no window opens, run codex mcp login boei in a terminal.

From the terminal:

codex mcp add boei --url https://app.boei.help/mcp
codex mcp login boei

The second command opens the Boei sign-in in your browser.

Connect from Claude Code

Claude Code is Anthropic's command-line assistant. Run this once:

claude mcp add --transport http --scope user boei https://app.boei.help/mcp

Then start Claude Code, type /mcp, choose boei, and pick Authenticate. The Boei sign-in opens in your browser.

Connect from Cursor

  1. Open Cursor Settings, then Tools & MCP (older versions: MCP), and click New MCP Server. Cursor opens a settings file for you.
  2. Paste this into it and save:

{
  "mcpServers": {
    "boei": {
      "url": "https://app.boei.help/mcp"
    }
  }
}

  1. Back in the settings list, Boei shows a Connect or Needs login button. Click it, sign in, and click Allow.

Connect from VS Code

  1. Open the Command Palette and run MCP: Add Server.
  2. Choose HTTP, paste https://app.boei.help/mcp, name it boei, and choose Global so it works in every project.
  3. VS Code asks whether the server may sign you in. Allow it, sign in to Boei, and click Allow.

Connect from Gemini CLI

Gemini CLI has no settings screen for this, so you add a few lines to its settings file at ~/.gemini/settings.json:

{
  "mcpServers": {
    "boei": {
      "httpUrl": "https://app.boei.help/mcp",
      "oauth": { "enabled": true }
    }
  }
}

Start Gemini CLI and run /mcp auth boei. The Boei sign-in opens in your browser.

Connect from Windsurf

Windsurf (also sold as Devin Desktop) has no form for this, so you add a few lines to its settings file. Click the MCPs icon at the top right of the Cascade panel, open the settings file, and paste:

{
  "mcpServers": {
    "boei": {
      "serverUrl": "https://app.boei.help/mcp"
    }
  }
}

Save and refresh the list. The Boei sign-in opens in your browser.

Connect from Zed

  1. Open Settings, then AI, then MCP Servers.
  2. Click Add Server, choose Add Remote Server, and paste https://app.boei.help/mcp.
  3. Zed asks you to sign in the first time it connects. Sign in and click Allow.

Connect from Cline

  1. Click the MCP Servers icon in the Cline panel and open the Remote Servers tab.
  2. Enter boei as the name, paste https://app.boei.help/mcp as the URL, and choose Streamable HTTP.
  3. Click Add Server. The Boei sign-in opens in your browser. If no sign-in appears, update Cline: browser sign-in was added in August 2026.

Connect from Goose

  1. Open the sidebar, click Extensions, then Add custom extension.
  2. Choose Remote Extension (Streamable HTTP), name it boei, and paste https://app.boei.help/mcp as the endpoint.
  3. Save. The Boei sign-in opens in your browser. Leave the client ID and secret fields empty.

Connect from another tool

Continue, JetBrains AI Assistant, Perplexity, Raycast, and most other AI tools work the same way. Look for "MCP server", "remote server", "connector", or "extension" in the tool's settings, paste https://app.boei.help/mcp, choose Streamable HTTP if it asks how to connect, choose OAuth if it asks how to sign in, and complete the sign-in when the browser opens. If the tool offers no way to sign in through the browser, it cannot connect to Boei yet.

What the assistant can do

  • Contacts: list, search, look up by email or phone, create, update, mark as customer, delete.
  • Deals: list, view, create, update, move between pipeline columns, archive, close as won or lost.
  • Deal activities: list the timeline, add tasks, calls and meetings, mark them complete.
  • Pipeline columns: list, add, rename, remove.
  • Inbox: list threads, read a conversation, log a message, change a thread's status, delete a thread.
  • FAQs: list, create, edit questions and answers.
  • Chatbot settings: change a chatbot's name, opening message, tone, instructions and rules, language, and blocked topics.
  • Chatbot training: list your chatbots, manage tags, add or edit training texts, add web pages and websites, start a crawl.

The assistant cannot chat with your visitors, upload files, create or delete chatbots, change a chatbot's AI model or design, or touch live-chat and integration settings through this connection.

Examples of what to ask

  • "Find the contact with email jane@acme.com and show her open deals."
  • "Move the Acme deal to Proposal and add a task to call them on Friday."
  • "Which inbox threads are still open from this week? Summarize them."
  • "Add a FAQ item: 'Do you ship abroad? Yes, to all EU countries.'"
  • "Train my support chatbot on https://example.com/returns-policy."
  • "Add a rule to my support chatbot: never quote prices, refer to sales instead."

Signing in as a different user

The approval screen shows which Boei account is being connected. Click Not you? to sign in with another account before approving.

Disconnecting

Remove the connector in your AI tool. The tool forgets its access and can no longer reach your Boei account. A connection also expires on its own: the tool has to renew its access every hour, and after 30 days without use it has to ask you to sign in again.

If you think a connection was set up by someone who should not have access, change your Boei password and contact us. We can cut off all connected tools for your account.

Troubleshooting

  • "Unauthenticated" or the tool asks to reconnect: the connection expired. Reconnect from the tool; you will be asked to sign in to Boei again.
  • "API access is not available on your current plan": your plan does not include API access. Upgrade, or contact us if you believe this is wrong.
  • Codex shows Boei in its list but cannot do anything: the sign-in did not finish. Run codex mcp login boei in a terminal and restart the app.
  • ChatGPT shows no Create button: Developer mode is off, or your workspace admin has not allowed custom connectors yet.
  • The tool says it cannot reach the server: check that you pasted https://app.boei.help/mcp exactly, including /mcp at the end.
  • The assistant cannot find something you can see in Boei: ask it to search again with the exact email or deal name. It works from the same data your login sees, so if you can see it, it can too.

Prefer to build your own integration instead? See the REST API and API authentication pages.