Brightalk.aiBrightalk.ai
Book a Demo

BRIGHTALK MCP

Your AI.Now with CRM access.

Give Claude or Codex a task. Brightalk MCP connects it to contacts, AI calls, automations, and SMS in the CRM your team already uses.

See setup stepsOpen MCP settings

Developer preview · Local connection · Requires Brightalk source access and an organization API key

brightalk / mcpInteractive example
Preview this message’s length, then send the content I confirm to the selected contact.

Brightalk tools

brightalk_preview_sms
brightalk_send_sms

After preview, submit the message and get an activity ID and queue status. Queued does not mean delivered.

Illustration only. Switching examples does not access data, place calls, or send SMS.

MODEL CONTEXT PROTOCOL

From a request to a CRM action.

MCP is a protocol that connects AI tools to external services. Brightalk MCP makes CRM capabilities available to your AI client, using your organization API key to authorize each query and action.

Claude / CodexBrightalk.aiMCPBrightalk CRM

GET CONNECTED

Connect your next conversation to your work.

Start with a query to verify the connection, then grant the actions your team needs. The same guide is available in Settings → API → MCP.

Available as a local developer preview

Requires a Brightalk source checkout, Node.js, and an organization with Public API enabled. A public package, remote MCP URL, and one-click OAuth connection are not available yet.

Contact us for setup access

Your organization’s limits apply

Calls, SMS, and workflows follow your existing plan and credit usage, with API key scopes, rate limits, and destination restrictions.

View plans and pricing
Choose how to start

This choice updates the example configuration and suggested scopes. Your API key controls actual access. After changing modes, update your client configuration and restart the MCP server.

  1. Prepare an organization API key

    Your organization must have Public API enabled. Use a bt_live_ key and select the scopes your tasks need. Existing keys do not gain new permissions automatically.

    Open MCP settings

  2. Prepare your local environment

    Obtain a Brightalk source checkout, install a Node.js version supported by its package.json, and run npm ci in the project root. Contact the Brightalk team if you do not have source access yet.

    Add the line below to .env.local in that checkout and replace the placeholder with your key. Preserve existing settings. Keep the key local; do not paste it into AI conversations or commit it to version control.

    .env.local
    BRIGHTALK_API_KEY=bt_live_REPLACE_WITH_YOUR_KEY

  3. Add Brightalk to your AI tool

    For example, /Users/you/brightalk or C:\Projects\brightalk. Used to generate the client configuration below.

    In Claude Desktop, open Settings → Developer → Edit Config and add the brightalk entry below.

    claude_desktop_config.json
    {
  "mcpServers": {
    "brightalk": {
      "command": "node",
      "args": [
        "/absolute/path/ai-native-crm/node_modules/tsx/dist/cli.mjs",
        "--tsconfig",
        "/absolute/path/ai-native-crm/tsconfig.json",
        "/absolute/path/ai-native-crm/scripts/brightalk-mcp.mts"
      ],
      "env": {
        "BRIGHTALK_MCP_READ_ONLY": "true"
      }
    }
  }
}

    If you already use other MCP servers, merge the brightalk entry and preserve your existing configuration. The configuration contains no API key; the server reads it from the Brightalk checkout’s .env.local at startup.

    Read the client’s official setup guide

  4. Verify with a query

    Save and restart the client or MCP connection. Check for tools starting with brightalk_, then try:

    Use Brightalk to list the first 5 contacts. Read only; do not change any data.

    Seeing the tools confirms that MCP started. A successful query, including an empty list, confirms API connectivity and permissions. SMS preview does not send a message, but still requires sms:send.

    Trouble connecting? Check these three things
    • Node not found: replace command with the absolute path to your Node executable. Find it with command -v node on macOS/Linux or where.exe node on Windows.
    • Authentication failed: confirm the key starts with bt_live_, has not expired or been revoked, and Public API is enabled for the organization.
    • Permission denied: check the tool’s required scope. Transcripts, recordings, and batches need their corresponding scopes selected separately.

Before you connect

Which AI tools can I use?

The local version includes examples for Claude Desktop, Claude Code, and Codex. Other clients that support stdio MCP can also connect. Services that only accept a remote MCP URL cannot connect directly yet.

Can I start with read-only access?

Yes. Query mode hides write and send tools, and your key can grant only the read scopes you need. SMS preview does not send, but still requires sms:send. Changing the mode here does not modify existing keys or a running MCP server; update your configuration and restart it.

Can AI create new automation workflows?

This version can start or cancel runs of existing workflows and check their status. Create and enable the workflow in Brightalk first. MCP does not edit workflow definitions yet.

Does a successful response mean the call or SMS is complete?

Not necessarily. Queued means the request was accepted. Query calls to track their progress. SMS has no dedicated status-query tool yet, and queued does not mean delivered. Reuse the same operation ID and content when retrying to avoid duplicate actions.

Does CRM data reach my AI client?

Yes. Tools return results within your authorized scope to the AI client you use. Follow your team’s approved AI services and data policies. The API key stays in your local configuration and is not returned as a tool result.