Connect Claude to growResonance

What you need

• Access to the workspace you connect. For the “Read and report back” permission, the Owner or Admin role.
• An active growResonance subscription (a trial is enough).
• For option A: a Claude account on claude.ai (Free, Pro, Max, Team or Enterprise).
• For option B: Claude Code or Claude Desktop in a version that supports MCP servers over HTTP.

Setup

MCP (Model Context Protocol) is an open standard that lets AI assistants connect to external data sources.

With the growResonance connection, your own Claude reads the data of your workspace: visibility, prompts, competitors, sources and sentiment, plus the recommendations including ready-made building blocks such as FAQ JSON-LD, schema markup, meta tags and draft texts. It can put them into practice where your website lives: in your repository, your CMS or your editor.

growResonance itself does not write anything on your website. Access is read-only; the only exceptions are checking off a completed recommendation and reporting back an article URL, so your dashboard stays in sync.

Two options: which one fits you?

Option A: connect Claude.ai by signing in

1. Copy the server address
   In growResonance, open Settings → Integrations and click “Connect” in the “Claude” row. On the “Connect AI” page, Claude is already selected; click “Connect with Claude”. This copies the server address to your clipboard and opens Claude in a new tab.
2. Add the connector in Claude
   In Claude, go to Customize → Connectors, click the plus icon and then “Add custom connector”. Paste the copied server address and confirm with “Add”. There is no field for a key here, and none is needed.
3. Confirm access
   Claude redirects you to growResonance. Sign in if you have not already, choose the workspace Claude may see, and confirm. You are then back in Claude and the connector is connected.
4. Turn it on in the chat and test it
   A connector works per conversation. In the chat, click the plus icon at the bottom left, then “Connectors”, and turn on growResonance. Then ask for your open recommendations. If a list comes back, the connection works.

Option B: Claude Code or Claude Desktop with a connection key

1. Check your permission
   Only owners and admins can create the connection key. You can see your role under Settings → Team. The key belongs to the workspace, not to you as a person, so it keeps working after a role change.
2. Create a connection key
   Open Settings → Integrations → “Claude” row (“Connect”, or “Manage connection” in the “…” menu), and on the “Connect AI” page click “Create connection key” in the bottom section “Alternative: static connection key”. The key is shown in full exactly once. Copy it right away and keep it like a password. After that you only see the prefix, for example “grmcp_ab12cd…”.
3. Add the key to Claude
   Enter the address and key in your MCP configuration (snippet below). In Claude Code this is the .mcp.json file in your project directory, in Claude Desktop the app’s MCP server configuration. Then restart Claude.
4. Test the connection
   Ask Claude for your open recommendations. If a list comes back, the connection works. In the settings you can also see when the key was last used.

Example configuration (.mcp.json)

{
  "mcpServers": {
    "growresonance": {
      "type": "http",
      "url": "https://www.growresonance.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer grmcp_YOUR_CONNECTION_KEY"
      }
    }
  }
}

What you can do with the connection

With the connection, Claude reads your growResonance analysis. Instead of copying findings out of the dashboard, you ask for them in the chat and have them implemented where your website lives.

• Ask about your own visibility per model, period and location, with the same numbers as in growResonance.
• Compare competitors and cited sources, and see the sentences in which a source appears in the answers.
• Get open recommendations sorted by priority and explained, including why a recommendation comes first.
• Use the ready-made artifact of a recommendation: FAQ JSON-LD, schema markup, meta tags or a draft text, added in the right place.
• Work through the issues from the last Technical Audit, each with affected page, severity and specific fix instructions, filterable by critical, warning and notice.
• Get the full text of a GEO article as Markdown or as finished HTML and move it into your CMS, repository or editor.
• Report back what is done: check off a recommendation or enter the live URL of a published article so the dashboard stays in sync.

What the connection accesses

Access is limited to 17 clearly defined tools. Claude does not get open access to your account but can query and report back exactly the following:

What the connection does NOT access

• No credentials: not your password, not the logins of connected accounts (for example Google), not stored API keys.
• No billing data: no invoices, no payment methods, no access to Stripe. From your plan, only the number of allowed prompts.
• No account or team data: no members, no email addresses, no roles, no invitations.
• No data from other workspaces, even if you own several.
• No dismissed recommendations: suggestions you have hidden stay hidden and cannot be brought back through the connection.
• Nothing created, nothing deleted: the connection cannot create or remove prompts, tasks, articles or audit runs.

Example prompts to try

• “How has our visibility developed over the last 30 days?”
• “Show me my open growResonance recommendations.”
• “Take the most important open recommendation and implement it in this repository.”
• “Get the FAQ schema from the recommendation and add it to the right page.”
• “Get the content of my latest growResonance article as Markdown.”
• “Show me the critical issues from my last Technical Audit and fix them in this repository.”
• “The recommendation is implemented. Mark it as done.”