Legal

GoBlinkly MCP Server

Last updated July 2026
On this page

The GoBlinkly MCP server lets you securely connect your GoBlinkly account to supported MCP clients, including Claude. Once connected, you can work with SEO analytics, AEO citation insights, website traffic data, and supported content workflows directly inside your MCP client.

Every connection is user-scoped. Each MCP session runs as the GoBlinkly user who completed the authentication process and follows that user's existing permissions within GoBlinkly.

What you can do

The GoBlinkly MCP connector supports workflows such as:

  • Reviewing brand-level SEO performance and trend data
  • Exploring Google Search Console data already available in GoBlinkly
  • Accessing GA4 traffic metrics through a brand's connected integrations
  • Analysing AEO citation visibility, share of voice, rankings, citation gaps, and prompt performance
  • Reviewing blog-generation jobs and their current status
  • Creating and managing blog content in supported GoBlinkly workflows
  • Publishing, unpublishing, and scheduling supported content

The available features depend on your permissions, brand access, and configured integrations.

Requirements

To connect GoBlinkly to an MCP client, you need:

  • An active GoBlinkly account
  • Access to at least one brand in GoBlinkly
  • An MCP client that supports remote connectors and OAuth authentication

The connector only provides access to data and actions that are already available to the authenticated user within GoBlinkly.

Connecting GoBlinkly to Claude

Once the GoBlinkly connector is available in the Claude Connectors Directory:

  1. Open Claude.
  2. Go to Customize.
  3. Select Connectors.
  4. Search for GoBlinkly.
  5. Select the GoBlinkly connector and click Connect.
  6. You will be redirected to the GoBlinkly login page.
  7. Sign in using your GoBlinkly account.
  8. Review and authorise the connection.
  9. Return to Claude and begin working with your GoBlinkly data.

Each user must connect using their own GoBlinkly account.

Authentication

GoBlinkly uses OAuth with PKCE for MCP connections. When you connect GoBlinkly:

  1. The MCP client starts the GoBlinkly authorisation flow.
  2. If you are not already signed in, you are redirected to the GoBlinkly login page.
  3. After login, GoBlinkly authorises the connection for that specific user.
  4. The MCP client exchanges the authorisation code for an access token and refresh token.
  5. Future MCP requests run as the authenticated GoBlinkly user.

The connection is tied to both the authorised MCP client and the GoBlinkly user who completed the login process.

You do not need to provide an API key, access token, OAuth client ID, or OAuth client secret during the normal connection process.

Permissions and security

GoBlinkly checks permissions on every MCP request. Security controls include:

  • You can only access brands you already have permission to view in GoBlinkly
  • Requests for unauthorised brands are rejected
  • MCP sessions are tied to an authenticated GoBlinkly user
  • Existing GoBlinkly roles and brand assignments remain the source of truth
  • Access tokens can be refreshed through the OAuth flow
  • Sessions and access can be revoked

The GoBlinkly MCP connector does not bypass the application's existing authentication or permission controls.

User access

  • Superadmins may access all brands available within their GoBlinkly organisation.
  • Standard users may access only the brands assigned to them.

Data access

Depending on your permissions and brand configuration, the connector may access:

  • Available brands and integration status
  • Aggregated SEO dashboard metrics
  • Historical search-performance data stored in GoBlinkly
  • Google Search Console query data already synced into GoBlinkly
  • GA4 traffic metrics through connected integrations
  • AEO citation analytics
  • Share-of-voice data
  • Citation gaps and topic rankings
  • Tracked prompts and prompt-run history
  • Blog workflow records
  • Blog-generation job states
  • Publishing and scheduling status

The connector does not grant access to brands or data that the authenticated user cannot access inside GoBlinkly.

Read and write capabilities

The GoBlinkly MCP connector supports both read-only analysis and action-based workflows.

Read capabilities

  • View SEO analytics and traffic trends
  • Review Google Search Console data
  • Analyse AEO citation performance
  • Review share-of-voice and ranking data
  • Inspect integration status
  • Review blog records and generation jobs
  • Check publishing and scheduling status

Write capabilities

Depending on the tools available and your permissions, you may be able to:

  • Create blog records
  • Retry or resume blog-generation jobs
  • Publish or unpublish content
  • Schedule content for future publication
  • Update an existing publication schedule

Write actions may modify or publish content in GoBlinkly. Review action details carefully before confirming them in your MCP client.

Example prompts

After connecting GoBlinkly, you can ask questions such as:

  • List the GoBlinkly brands I can access.
  • Summarise SEO performance for my brand over the last 30 days.
  • Show recent website traffic trends.
  • What are our highest-performing Google Search Console queries?
  • Show our latest AEO share-of-voice data.
  • Identify our most important citation gaps.
  • Compare our visibility with tracked competitors.
  • Show tracked prompts where competitors rank above us.
  • List recent blog-generation jobs and their statuses.
  • Show failed blog jobs that can be retried.
  • Schedule this approved blog for publication.
  • Unpublish the selected blog.

The exact prompts and actions available depend on the tools exposed by the current connector version.

Disconnecting GoBlinkly

You can disconnect GoBlinkly from Claude at any time:

  1. Open Claude.
  2. Go to Customize.
  3. Select Connectors.
  4. Find GoBlinkly.
  5. Open the connector settings.
  6. Select Disconnect.

After disconnection, Claude will no longer be able to access GoBlinkly through that connection.

Troubleshooting

The connector cannot find a brand

Confirm that:

  • The brand is visible in your GoBlinkly account
  • You signed in using the correct GoBlinkly account
  • Your user has been assigned access to the brand

Analytics data is unavailable

Confirm that the required integration, such as Google Search Console or GA4, is connected for the selected brand. Some data may also be unavailable for the requested date range.

An action is rejected

The authenticated user may not have permission to perform the requested action, or the selected content may not be in a valid state for that action.

The connection stopped working

Disconnect and reconnect the GoBlinkly connector. If the issue continues, contact GoBlinkly support and include the error message and approximate time of the issue.

Privacy

For information about how GoBlinkly processes and protects data, see the GoBlinkly Privacy Policy.

Support

For help with GoBlinkly MCP access, permissions, integrations, or connector errors, contact [email protected].

When contacting support, include:

  • The MCP client used
  • The GoBlinkly account email used to connect
  • The affected brand
  • What you were trying to do
  • The approximate time of the issue
  • Any error message displayed

Do not include passwords, OAuth client secrets, access tokens, or other private credentials in a support request.