MCP Integration: Connect an AI Client

What MCP integration does

MCP (Model Context Protocol) lets a compatible AI client call selected BNex tools after you authorize a connection. The connection is bound to the person who created it, the selected workspace, the client credential, and the scopes you approved.

BNex is not exposed as a general database, shell, arbitrary REST proxy, or unrestricted agent. Every tool call re-checks the grant, current workspace membership, scope, and applicable BNex permission.

• Workspace overview: workspace display name and WhatsApp setup state.
• Contact search: a small set of matching display names and masked phone numbers.
• Recent conversations: bounded recent thread previews; internal notes are excluded and phone/email patterns are masked.
• Campaign analytics: recent campaign names/statuses and aggregate counts, without recipient lists.

Create a personal agent connection

1. Open Advanced Settings → MCP agents. Sign in to the workspace and open Advanced Settings. The MCP agents section is available to workspace Owners and Admins.
2. Name the connection and select only needed access. Enter a connection name and select one or more supported scopes: workspace overview, contact search, recent conversations, and campaign analytics. Start with the minimum access needed.
3. Create the connection. BNex binds the credential to your authenticated user and current workspace. The bearer token is displayed once in the connection panel.
4. Copy the URL and token into your client. Use the server URL and token from that panel. Do not use an organization ID or invent a server URL.
5. Run the connection check. Use BNex’s “Authorize token” action to perform an MCP initialize handshake. This verifies the credential but does not invoke a tool or read workspace data.
6. Close the panel only after saving the token. BNex cannot reveal the plaintext token again after the panel closes. If it is lost, revoke the connection and create a replacement.

Generic Streamable HTTP configuration

BNex uses stateless Streamable HTTP. For a compatible client that accepts a remote MCP URL and custom HTTP headers, use the generated configuration from the BNex connection panel. Replace placeholders only with the exact URL and bearer token shown there.

The following shows the configuration shape. It is not a reusable credential: endpoint and token values are unique to your connection.

{
  "mcpServers": {
    "bnex": {
      "url": "<MCP server URL copied from BNex>",
      "headers": {
        "Authorization": "Bearer <one-time token copied from BNex>"
      }
    }
  }
}

Client-specific setup notes

The backend documents the Streamable HTTP transport and BNex’s generated URL-plus-Authorization-header configuration shape. It does not certify every vendor client or provide vendor-managed marketplace registrations for all clients. Before following a client-specific path, confirm that the client supports remote Streamable HTTP MCP servers and custom bearer headers.

• API keys, webhooks, and dataUnderstand why API keys and MCP agent tokens are different.
• Team access and rolesReview who can create and revoke workspace connections.

Claude Desktop

BNex does not document a Claude Desktop-specific config file path or certify a local-stdio bridge. Use the BNex-generated JSON only if the Claude Desktop version and setup path you use accepts a remote Streamable HTTP server with a custom Authorization header. If its setup requires a local command instead, BNex does not provide that command; do not paste a bearer token into an untrusted bridge.

Cursor

If your Cursor MCP settings accept the remote URL and custom headers in the generic configuration above, paste the BNex-generated JSON there and save it in the client’s private settings. BNex does not publish a Cursor-specific config-file path or guarantee a Cursor release’s compatibility; verify the connection with the client’s MCP status and BNex initialize check.

Claude Code

BNex does not publish a Claude Code command line or per-project config recipe. Connect only through a Claude Code MCP configuration mode that supports remote Streamable HTTP and a bearer Authorization header. Keep workspace tokens out of shared project configuration and source control.

Codex App and ChatGPT

The backend documentation says live marketplace/client registration details and end-to-end connector tests are still required for ChatGPT and Codex. BNex therefore does not claim a ready-made marketplace connector for these products. An administrator must not guess a client identifier or OAuth callback URL; registered OAuth clients require exact marketplace-issued values.

Hermes Agent and other MCP clients

BNex has no Hermes-specific setup instructions or verified-client statement in its current backend documentation. A client can use the BNex server only if it supports remote Streamable HTTP, custom bearer headers, and the generated configuration shape. Ask your workspace administrator to confirm approved client use before connecting customer data to a third-party agent.

Scopes, permissions, and current limits

• Workspace overview access returns only the workspace display name and WhatsApp setup state.
• Contact search is bounded to 10 results and returns masked phone numbers rather than contact IDs or full records.
• Recent conversation reads are bounded to 10 threads and up to 5 recent previews per thread; internal notes are excluded.
• Campaign analytics returns at most 20 recent campaigns and aggregate outcomes, not recipient data.
• The template-send scope is disabled in the current Settings UI. It must not be treated as an available feature even though a server-side tool name exists.
• BNex currently has no verifiable affirmative opt-in evidence/source and timestamp for contacts. A contact not marked opted out is not proof of consent; MCP template sending fails closed.
• Campaign launch, generic sends, billing changes, contact mutation, template management, credentials, and destructive actions are not exposed as MCP tools.

Review and revoke an agent connection

1. Return to Advanced Settings → MCP agents. Review the listed workspace connections and their names/scopes.
2. Revoke a connection you no longer need. Use the revoke action for the relevant connection. Revocation invalidates its MCP grant and tokens immediately.
3. Remove access when a teammate leaves. Update workspace membership and revoke connections as part of offboarding. BNex checks current membership and permission for every tool call.

• Workspace settingsOpen Advanced Settings.
• Team access and rolesReview member access and offboarding.
• Troubleshooting and supportResolve a failed MCP connection.

Frequently asked questions