BrightEdge MCP
Connect AI Tools to BrightEdge Data
Overview
What is an MCP Server?
MCP stands for Model Context Protocol - an open standard that lets AI assistants (like Claude and ChatGPT) securely connect to external data sources and tools.
Before MCP, getting data into an AI workflow meant manual exports, spreadsheet uploads, or writing custom code. MCP removes that friction. Once a connection is established, you simply ask a question in plain language, and AI is leveraged to fetch the data, perform the analysis, and return an insight, all in a single step.
Key properties of a BrightEdge MCP connection:
- Secure: Authentication uses OAuth 2.0.
- Read-only: BrightEdge MCP tools retrieve data only. Nothing in your BrightEdge account is modified.
- Real-time: Data is pulled live from your BrightEdge account at query time.
Why BrightEdge MCP?
BrightEdge has spent over a decade building the industry's most comprehensive SEO and AEO datasets. The MCP server puts that data directly inside your AI workflow, so you spend less time pulling reports and more time acting on insights.
The BrightEdge MCP combines proprietary data — DataCube X, AI HyperCube, Keyword Reporting, Share of Voice, Analytics Reporting, Google Search Console, AI Catalyst, Recommendations, and AI Agent Insights with the reasoning capabilities of a large language model. Questions that used to require opening multiple dashboards, running several exports, and combining results in a spreadsheet can now be answered with a single, well-structured prompt.
The biggest cost in AEO and SEO workflows is not the analysis itself; it is the time between a question arising and an answer being ready to act on. BrightEdge MCP compresses that gap dramatically:
| Without MCP | With BrightEdge MCP |
|---|---|
| Export keyword, prompt, and other data from BrightEdge | Ask a question in plain language |
| Export GSC data from Google, or analytics data from your web analytics platform | MCP fetches from both sources simultaneously |
| Combine datasets in a spreadsheet | LLM cross-references and synthesizes automatically |
| Interpret results and write a summary | Receive a ready-to-act insight |
| Hours per analysis | Seconds/minutes per analysis |
Connection Details
Use the following endpoints depending on your platform's transport requirements:
| Setting | Value |
|---|---|
| MCP Endpoint (HTTP) | https://mcp2.brightedge.com/mcp |
| SSE Endpoint | https://mcp2-sse.brightedge.com/sse |
Who Can Access BrightEdge MCP?
All BrightEdge customers with a valid set of BrightEdge login credentials (including username and password) can connect to the MCP server.
You can use your existing credentials to connect to and query the MCP server within the defined usage limits. For any questions or concerns, please reach out to the BrightEdge team at integrations@brightedge.com.
Authentication
All platforms use OAuth 2.0 authentication. When prompted during setup, you will sign in with your BrightEdge account credentials. BrightEdge uses Auth0 as its identity provider — you will see a BrightEdge-branded login screen hosted on auth0.com.
Available Setup Guides
- ChatGPT: OAuth setup via ChatGPT Settings → Plugins
- Claude: Custom connector via Claude Settings → Connectors
- Gemini Enterprise: Custom MCP server in Gemini Enterprise
- Lovable: Custom connector via Lovable Settings → Connectors
- Manus: Custom MCP via SSE transport + Bearer token
- Microsoft Copilot: MCP tool in Copilot Studio with OAuth
- n8n: MCP Client node with OAuth2 — HTTP Streamable transport
- OpenClaw: Mcporter middleware + terminal configuration
- Relevance AI: MCP tool added via agent configuration with OAuth
- Slack: Pre-configured app, connect account via Slack desktop
ChatGPT
Platform 1 of 10
Connect BrightEdge MCP to ChatGPT on the web to query BrightEdge data directly within your ChatGPT conversations.
BrightEdge's MCP server is available in OpenAI's Plugin repository. You can access it directly via Plugins, and enter your BrightEdge credentials to authenticate and start prompting. The Plugin available in OpenAI's Plugin marketplace has the MCP Endpoint: https://mcp.brightedge.com/marketplace/v2
Alternatively, customers can set up a custom plugin for BrightEdge using the instructions below, and that would always reference the most up-to-date tools. Please note that to create a custom plugin, you need to have Developer mode turned on via Settings → Security and login → Developer mode.
- An active BrightEdge account
- A ChatGPT Pro or Plus account
| Setting | Value |
|---|---|
| Server URL / MCP Endpoint | https://mcp2.brightedge.com/mcp |
Navigate to chatgpt.com and log in. Click your profile icon in the bottom-left corner and select Settings.
In Settings, select the Apps section, then click Create app.
Fill in the following fields. Leave all other pre-populated fields as they are:
- Server URL:
https://mcp2.brightedge.com/mcp OAuth Client ID
Please reach out to your Customer Success Manager or the Support team to request the OAuth Client ID, which is required to complete the MCP server setup.- OAuth Client Secret
Leave the Resource with DNS URL field as pre-populated, then click Create.
Note: You may need to click into Advanced Auth settings to view all the required fields.
A BrightEdge login screen will appear. Enter your BrightEdge account credentials and click Log In. Once authenticated, the connector will be added to your account.
Close the settings dialog. In the chat interface, click the + icon in the message input area, then select More. Select the BrightEdge connector you just created to activate it for the current conversation.
With the connector active, you can now query BrightEdge data directly in ChatGPT.
Claude
Platform 2 of 10
Connect BrightEdge MCP to Claude on the web (claude.ai) or via the Claude desktop application. Claude uses OAuth authentication and provides per-tool permission controls once connected.
- An active BrightEdge account
- A Claude account (any paid plan)
| Setting | Value |
|---|---|
| Remote MCP Server URL (Web) | https://mcp2.brightedge.com/mcp |
| Authentication | OAuth (Auth0) |
Launch Claude and click on your profile name in the bottom-left corner. Select Settings from the dropdown.
In the Settings menu, locate and click Connectors. You will see existing integrations (such as Google Drive and GitHub).
Click Add custom connector and fill in the following fields:
- Name: BrightEdge MCP
- Remote MCP Server URL:
https://mcp2.brightedge.com/mcp OAuth Client ID
Please reach out to your Customer Success Manager or the Support team to request the OAuth Client ID, which is required to complete the MCP server setup.
Expand Advanced settings if the Client ID field is not immediately visible. Click Add to save the connector.
The BrightEdge connector will now appear in your connectors list. Click Connect. Claude will redirect you to a BrightEdge OAuth/Auth0 login screen. Enter your BrightEdge email and password, then click Log In. Once authenticated, Claude will securely link the connector to your account.
After connecting, Claude will display the list of tools exposed by the BrightEdge MCP server. For each tool you can set the permission to Allowed, Blocked, or Ask every time. For uninterrupted use, set Read-only tools to Allowed.
The BrightEdge connector is now active. In any chat, ensure the BrightEdge connector is enabled (visible in the chat toolbar), then start prompting.
Gemini Enterprise
Platform 3 of 10
Connect BrightEdge MCP to Gemini Enterprise as a custom MCP data store, giving Gemini agents access to live BrightEdge data. Setup happens in two stages: an admin registers the connector once at the organization level in the Google Cloud console, then each user authorizes their own access from the Gemini Enterprise chat interface.
- An active BrightEdge account
- Gemini Enterprise admin access, to register the connector as a data store
- Discovery Engine Editor role (
roles/discoveryengine.editor) on the relevant Google Cloud project
| Setting | Value |
|---|---|
| MCP Server URL | https://mcp2.brightedge.com/mcp |
| Authentication | OAuth 2.0 (Auth0) |
In the Google Cloud console, go to Gemini Enterprise → Data Stores. Click Create data store, then search for and select Custom MCP Server.
Fill in the following fields:
- MCP Server URL:
https://mcp2.brightedge.com/mcp - Authorization URL
- Token URL
- OAuth Client ID
- OAuth Client Secret
- Scope:
openid profile email
In the MCP Server Description field, describe what BrightEdge MCP does and when the agent should use it — for example, "Provides SEO and AI visibility data, including keyword rankings, competitor gaps, and AI citation tracking, for the connected domain." Gemini relies heavily on this field to decide when to invoke the connector, so avoid vague descriptions. Optionally, use the MCP Agent Instructions field to tell the agent which tool to call for which type of question.
Click Continue, choose a location, name the data store (e.g. "BrightEdge MCP"), and click Create.
Once the data store status changes to Active, open it and select the Actions tab. Click Reload custom actions to pull in BrightEdge's tool list, select the tools you want available (up to 100 at a time), then click Enable actions.
Navigate to Apps, select the app you want to use (or create one), then go to Connected data sources. Click Add existing data stores, select the BrightEdge data store you just created, and click Connect.
Each user needs to authorize the connection individually. Open the Gemini Enterprise chat, click the connector icon in the message input area, and locate BrightEdge in the list. If it shows Authorize, click it and sign in with your BrightEdge account credentials on the Auth0-hosted login screen. Once authorized, the connector will show a toggle in place of the Authorize button — make sure it's switched on.
To avoid confusing results, toggle off other connectors you're not using for this task (e.g. Google Search), especially while testing.
Reference the connector by name rather than the term "MCP" — the agent reliably invokes tools when prompted with phrasing like "Using BrightEdge connector, find server info", but can fail to recognize "MCP" as a trigger. If the connector doesn't respond, try re-running the same prompt or starting a new chat.
Troubleshooting
Tool list looks incomplete: Asking for the full list of tools may return only a handful, seemingly at random. This appears to be an output-length limitation rather than a connection issue — ask for tools related to a specific task instead of requesting the full list.
Connector won't authenticate or respond: If Authorize doesn't redirect to a login screen, try the flow in an incognito window, or sign out and back into your Google session first. If a query times out or returns a server error, retry the same prompt, or start a new chat if retrying doesn't help.
Works for one user but not another on identical setup: This has been observed intermittently and doesn't appear tied to configuration. Retrying after a short wait has resolved it in past cases.
Lovable
Platform 4 of 10
Connect BrightEdge MCP to Lovable via its personal connector's settings. Lovable uses OAuth authentication and supports both HTTP and SSE endpoints.
- An active BrightEdge account
- A Lovable account (lovable.dev)
| Setting | Value |
|---|---|
| Server URL (SSE) | https://mcp2-sse.brightedge.com/sse |
| Authentication | OAuth |
Navigate to lovable.dev and sign in with your account credentials.
Click Settings in the navigation menu or from your profile dropdown.
In Settings, select Connectors. In the Personal connectors section, click Custom.
Fill in the connector form with the following values:
- – Server URL:
https://mcp2-sse.brightedge.com/sse - – Authentication: OAuth
- – OAuth Client ID
- – OAuth Client Secret
Click Add (or Connect) to proceed.
A BrightEdge authorization screen will appear. Select your workspace and click Allow to grant Lovable access.
Once connected, BrightEdge MCP will appear as "Enabled" in your Personal Connectors list. You can now use BrightEdge data in your Lovable projects and prompts.
Manus
Platform 5 of 10
Connect BrightEdge MCP to Manus using a direct SSE configuration. Manus supports custom MCP servers via its Connectors panel, with Bearer token authentication.
- An active BrightEdge account
- A Manus account (web or desktop)
| Setting | Value |
|---|---|
| Server URL (SSE) | https://mcp2-sse.brightedge.com/sse |
| Auth Header Value | Bearer <your-brightedge-token> |
In the Manus interface, locate the prompt input area. Click the Connect apps button (the second icon in the toolbar below the prompt input). This opens the connector options.
A list of available connectors will appear. Scroll to the bottom and click + Add connectors. This opens the full Connectors dialog.
In the Connectors dialog, click the Custom MCP tab at the top. If no custom MCPs have been added yet, you will see a message saying 'No custom MCP added yet'.
Click the + Add custom MCP dropdown button and select Direct configuration from the options (the alternative is Import by JSON). This opens the MCP configuration form.
Fill in the MCP configuration form with the following values:
- Server Name: BrightEdge
- Transport Type: SSE
- Server URL:
https://mcp2-sse.brightedge.com/sse
In the Custom headers section, click + Add custom header and enter:
- Header name:
Authorization - Header value:
Bearer <your-brightedge-token>
The Icon and Note fields are optional.
<your-brightedge-token> with your BrightEdge API token. Contact your BrightEdge team if you do not have a token.Click Save or Try it out to test before saving. BrightEdge will appear in the Custom MCP tab, confirmed with a green checkmark.
Close the connector dialog. Click Connect apps again — BrightEdge will now appear in the connector list and will be enabled by default. You can now include BrightEdge data in any Manus task or prompt.
Microsoft Copilot
Platform 6 of 10
Add BrightEdge MCP as a tool in Microsoft Copilot Studio to give your Copilot agents access to live BrightEdge data.
- An active BrightEdge account
- Access to Microsoft Copilot Studio (copilotstudio.microsoft.com)
| Setting | Value |
|---|---|
| Server URL | https://mcp2.brightedge.com/mcp |
Navigate to copilotstudio.microsoft.com and log in with your Microsoft credentials.
In the left panel, navigate to Agents and click New Agent (or open an existing agent). Provide a name, description, and select GPT-4o or your preferred model.
From within your agent, navigate to the Tools section and click Add Tool → Create New → Select MCP.
Fill in the following fields:
- Server URL:
https://mcp2.brightedge.com/mcp - OAuth Client ID
OAuth Client Secret
Please reach out to your Customer Success Manager or the Support team at integrations@brightedge.com to request the OAuth Client ID and Client Secret, which are required to complete the MCP server setup.- Auth URL:
https://be-mcp-server-v2-gigjheawsa-uc.a.run.app/authorize - Token & Refresh URL:
https://be-mcp-server-v2-gigjheawsa-uc.a.run.app/token - Scope:
openid profile email
Click Create. A Redirect URL will be generated.
Return to your agent and add the BrightEdge tool from the Tools section. A login screen will appear — enter your BrightEdge credentials to establish the connection.
Navigate to the Tools section of your agent and confirm that the BrightEdge MCP tool is shown as installed and active.
Navigate to your agent and begin prompting. The agent can now call BrightEdge tools to answer queries.
n8n
Platform 7 of 10
Connect BrightEdge MCP to n8n to incorporate live BrightEdge data into automated workflows and multi-step pipelines. n8n uses the MCP Client node with OAuth2 authentication.
- An active BrightEdge account
- An n8n account (cloud or self-hosted)
| Setting | Value |
|---|---|
| Server Transport | HTTP Streamable |
| MCP Endpoint URL | https://mcp2.brightedge.com/mcp |
| Authentication | MCP OAuth2 |
In n8n, navigate to Workflows and click Create workflow. This opens a blank workflow canvas.
On the workflow canvas, click Add first step (or the + icon). In the node search panel, search for MCP Client and select it to add it as a step.
With the MCP Client node selected, open the Parameters tab and set the following:
- – Server Transport: HTTP Streamable
- – MCP Endpoint URL:
https://mcp2.brightedge.com/mcp - – Authentication: MCP OAuth2
For the Credential for MCP OAuth2 API field, click Create New Credential. A credential form will open — enter the following values:
- – Use Dynamic Client Registration: Off (toggle off)
- – Grant Type: Authorization Code
- – Authorization URL:
https://mrkt-0365.us.auth0.com/authorize - – Access Token URL:
https://mrkt-0365.us.auth0.com/oauth/token - – Client ID
- – Client Secret
Click Save, then click Connect to MCP. A BrightEdge login page will open — enter your BrightEdge credentials to complete the OAuth flow.
Once authenticated, return to the MCP Client node. In the Tool dropdown, select the BrightEdge tool you want to use. Set Input Mode to Manual and enter your prompt in the Values to Send field.
Example prompt: show me ranking between Jan to Feb 2026
Click Execute step (or Execute workflow if you have multiple nodes) to run the workflow. BrightEdge data will be returned as the node output.
You can chain the MCP Client node output into further n8n nodes — for example, sending results to Slack, writing to a Google Sheet, or triggering further logic.
OpenClaw
Platform 8 of 10
Connect BrightEdge MCP to OpenClaw using mcporter, a middleware CLI that bridges OpenClaw with external MCP servers. Setup involves enabling mcporter in the OpenClaw UI and configuring it via the terminal.
- An active BrightEdge account
- Access to OpenClaw
- Node.js and npm installed
| Setting | Value |
|---|---|
| Server URL (SSE) | https://mcp2-sse.brightedge.com/sse |
In the OpenClaw UI, navigate to Skills in the left navigation menu. Locate mcporter in the Built-in Skills list and toggle it on.
Then install mcporter globally via npm by running the following command in your terminal:
npm install -g mcporter
Add the BrightEdge MCP server configuration to your local mcporter setup. Navigate to the .mcporter folder (create it if it doesn't exist):
cd $HOME/.mcporter/
Create or update credentials.json with the following content:
{
"version": 1,
"entries": {
"brightedge|fc7a79fb09a7771d": {
"serverName": "brightedge",
"serverUrl": "https://mcp2.brightedge.com/mcp",
"clientInfo": {
"client_id": "NM9It06JLxFxSASeXvxdoEveq01Uhohv"
}
}
}
}Create or update mcporter.json with the following content:
{
"mcpServers": {
"brightedge": {
"baseUrl": "https://mcp2.brightedge.com/mcp",
"auth": "oauth"
}
}
}Run the authentication command to link your BrightEdge account:
mcporter be-mcp auth
A BrightEdge login page will open in your browser. Enter your credentials and sign in. To verify the connection is active, run:
mcporter list
With authentication complete, use the /skill command in OpenClaw to query BrightEdge:
/skill <mcp_server_name> <query> /skill brightedge Get me the top 3 keywords for this month.
BrightEdge data will be returned directly within your OpenClaw workflow.
Relevance AI
Platform 9 of 10
Connect BrightEdge MCP to Relevance AI to give your agents and tools access to live BrightEdge data within automated workflows.
- An active BrightEdge account
- A Relevance AI account
| Setting | Value |
|---|---|
| Server URL | https://mcp2.brightedge.com/mcp |
In Relevance AI, navigate to the Agent or Tool you want to connect BrightEdge MCP to. Open its settings or configuration panel.
Look for the Integrations, Tools, or MCP section within the agent configuration. Click Add tool or Add integration.
When prompted for a tool type, choose MCP Server or Model Context Protocol.
Fill in the following fields:
- – Server URL:
https://mcp2.brightedge.com/mcp - – OAuth Client ID
- – OAuth Client Secret
- – Auth URL:
https://mrkt-0365.us.auth0.com/authorize - – Token URL:
https://mrkt-0365.us.auth0.com/oauth/token - – Scope:
openid profile email
Click Connect or Save. A BrightEdge login screen will appear — enter your BrightEdge credentials to complete the OAuth flow. Once authenticated, the connection will be confirmed.
Save the configuration. Test the connection by running a sample query within Relevance AI to confirm BrightEdge data is returned successfully.
Using BrightEdge Data in Workflows
Once connected, your Relevance AI agents can query BrightEdge data as part of any workflow step. When building prompts or agent instructions, be specific about which BrightEdge data you need and how you want it used.
Example agent instruction:
When the user asks about keyword performance, use the BrightEdge MCP tool to retrieve the relevant keyword data and summarise the findings in plain language.
Slack
Platform 10 of 10
The BrightEdge Slack App connects BrightEdge data and actions directly into your Slack workspace using Slack's standard OAuth installation flow. Installation takes only a few minutes and requires no technical configuration.
- An active BrightEdge account
- A Slack account with access to the workspace where the app will be installed
- Workspace admin approval may be required if your organisation restricts third-party app installations
Use the following link to begin the installation. Open it in a browser while signed in to your Slack account:
https://slack.com/oauth/v2/authorize?client_id=10825199192177.11032644384785&scope=app_mentions:read,assistant:write,channels:history,chat:write,im:history,users:read&user_scope=
Open the installation URL above in any modern browser while signed in to your Slack account. This launches Slack's official OAuth installation flow.
Slack will prompt you to select the workspace where the BrightEdge App will be installed.
- If you are signed in to multiple workspaces, choose the correct one from the workspace switcher.
- If you are not signed in, Slack will ask you to sign in first.
Slack will display the list of permissions (OAuth scopes) requested by the BrightEdge App. Review them before continuing. Permissions include:
- Reading user and channel information
- Reading message history (channels and direct messages)
- Posting messages
Click Allow to grant the requested permissions and complete the installation. Once approved, Slack installs the app into your selected workspace. You may be redirected back to BrightEdge or to a Slack confirmation page.
After installation, verify that the BrightEdge App is available in your workspace:
- Open Slack.
- Go to Apps in the left sidebar.
- Search for BrightEdge.
- Confirm the app is listed and accessible.
Troubleshooting
Missing Permissions: If installation fails, confirm the installer has the required role in the Slack workspace. Some permission scopes can only be approved by a workspace admin or owner.
Workspace Restrictions: Some Slack workspaces restrict third-party app installations. In that case, a workspace admin must approve the BrightEdge App before it can be installed.
Reinstalling the App: If the app was previously installed and its requested scopes have changed, a reinstall may be required for the new permissions to take effect. Simply open the installation link again and follow the same steps.