Connect Bolt to growResonance
Connect growResonance to your Bolt project as a custom MCP server.
What you need
- The Owner or Admin role in the growResonance workspace.
- An active growResonance subscription (a trial is enough).
- A Bolt project in which you can manage connectors.
Setup
Bolt can connect custom MCP servers. Once growResonance is connected, the Bolt chat knows your open recommendations including ready-made building blocks and implements them directly in the project you are working on.
- 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. - Create a connection key
Open Settings → Integrations, click “Connect” in the “Bolt” row and then “Create connection key”. The key is shown in full exactly once. Copy it right away. After that you only see the prefix, for example “grvibe_ab12cd…”. The server address to copy is on the same page. - Open connectors in Bolt
In the Bolt chat window, click the plus icon and choose “Connectors”. Open “Manage connectors” and click “Custom MCP server”. - Enter address, transport and key
Give it a name and paste the server address. Choose “HTTP” as the transport type, not SSE: the endpoint works statelessly over HTTP. Under authentication, choose “API key” and paste your connection key. - Test the connection
Ask the Bolt chat for your open growResonance recommendations. If a list comes back, the connection works. In growResonance, the Bolt card then shows a timestamp under “Last used”.
Server address
https://www.growresonance.ai/api/mcpWhat you can do with the connection
With the connection, Bolt 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. Bolt does not get open access to your account but can query and report back exactly the following:
| Tool | Which data | Direction |
|---|---|---|
| Workspace overview | Brand and domain, measured models and measurement frequency, markets, locations, number of competitors, last completed run, active prompts and plan limit, Search Console status. | reads |
| Get visibility | Visibility, share of voice, average position and sentiment of your own brand per model, period and day, with the change from the previous period. | reads |
| List prompts | Your prompts with ID (P-n), status, overall visibility and visibility per model in the last run, trend, mentions and average position. | reads |
| Get a prompt with answers | One prompt with its history and, per model, the answer from the last run: mentioned yes or no, position, brands named, cited sources and answer text. | reads |
| Compare competitors | Ranking of all brands with visibility, share of voice, average position, sentiment, citation rate and visibility per model. | reads |
| List sources | Most cited domains and pages with number of citations, prompts, models, source type and the share of answers that name your brand. | reads |
| Source details | One domain with citation rate, pages, citations per model and day, and the sentence from the answer in which the source appears. | reads |
| Get sentiment | Sentiment toward the brand (0–100), positive, neutral and negative shares, praise and criticism per attribute with verbatim sentences, comparison with competitors. | reads |
| List researched prompts | Prompts from Prompt Research with area, intent, demand, Google and AI search volume, evidence and status. | reads |
| Get Search Console data | Clicks, impressions, CTR and average position from the connected Search Console, plus the strongest queries and pages. Only the numbers, never access to Google. | reads |
| List recommendations | Your open and in-progress tasks from the AEO Strategy: ID (for example A-48), key, type, category, status, priority, title, rationale and the kind of attached artifact. | reads |
| Get a recommendation | A single task with steps, acceptance criteria and affected page, plus, if available, the ready-made building block to use: FAQ JSON-LD, schema markup, meta tags or a draft text. | reads |
| List articles | Your GEO articles: title, slug, status, GEO score, word count, archetype and the live URL, if published. | reads |
| Get article content | The full text of an article as Markdown and as complete HTML, plus the meta description. | reads |
| List audit issues | The findings of the last completed audit run (page speed, AI optimization and SEO), each with severity, affected page URL and fix instructions. | reads |
| Mark a recommendation as done | Sets a task to done, like checking it off in the AEO Strategy. Safe to repeat; dismissed tasks stay dismissed. | writes |
| Report an article as published | Enters the live URL of an article that is already published and sets its status to published. | writes |
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 recommendation and implement it in this project.”
- “Get the meta tags from the recommendation and add them to the page.”
- “Show me the critical issues from my last Technical Audit.”
- Bolt: connect MCP (official documentation) – Bolt’s menus, in the original.
Troubleshooting and FAQ
Which transport type do I need?
HTTP. The growResonance endpoint works statelessly and answers each request directly with JSON; there is no permanently open SSE stream. If SSE is selected, the connection stays silent without an error message.
Do I need to write “Bearer” in front of the key?
Try without it first: with “API key” selected, Bolt usually adds the word itself. If the connection stays silent, enter the value again as “Bearer grvibe_…”. You can see whether it worked in growResonance: as soon as a request arrives, “Last used” fills in.
I didn’t copy the key. How do I get it back?
You can’t: we store the key only as a one-way checksum, not in plain text. Create a new key in the settings (the old one automatically stops working) and enter it on the platform again.
Can I revoke the key?
Yes, at any time. On the platform page (Settings → Integrations, “…” menu of the platform’s row → “Manage connection”) you revoke it with one click. It stops working immediately, and the connection set up with it loses access right away. The keys of the other platforms are not affected.
Do I need a separate key for each platform?
Yes, on purpose: each workspace has exactly one active key per platform. That way Lovable, Bolt and Base44 can be connected at the same time, and you can revoke one connection without affecting the others.
The card still shows “Never used”.
Then no request with this key has reached us yet. Most common causes: the key was pasted incompletely (the prefix “grvibe_” is part of it), the server address is incomplete, or the connection was set up on the platform but not yet used in a chat. The timestamp only appears after the first real request.
Does this require a specific plan?
The connection is included in all active plans, including the trial. It is read access to data you already see in the dashboard. Anyone with access to the workspace can connect: members with the “Read only” permission, owners and admins also with “Read and report back”. If your subscription expires, access pauses until there is an active plan again; the connection itself stays in place and works again afterwards.
Is there a request limit?
Yes, 60 requests per minute per workspace. Setting up a connection takes two to three requests, each tool call one; even 20 tool calls in a minute use only a third of the limit. The limit protects against endless loops, not against your work. If it is reached, the server responds with “Too many requests”. Waiting one minute is enough.
Does growResonance see what the AI does with the data?
No. The AI runs in your own environment and works there with your permissions. growResonance only logs which tool was queried when and for which workspace, for traceability and abuse protection. Your conversations, your code and your files are not visible to us.