Connect Base44 to growResonance

Connect growResonance to your Base44 project as a custom MCP server.

Set up in Settings Start free trialIncluded in all active growResonance plans. On Base44, from the Builder plan.

What you need

The Owner or Admin role in the growResonance workspace.
An active growResonance subscription (a trial is enough).
On Base44, at least the Builder plan. Lower plans have no custom MCP connections.

Setup

Base44 connects custom MCP servers through the account settings. Once growResonance is connected, the Base44 editor chat knows your open recommendations including ready-made building blocks and implements them directly in the project you are building.

Important: Base44 is the only one of the three platforms that needs a header you put together yourself. You enter not just the key but the complete value, including the word “Bearer” and a space. This is where setup fails most often.

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 “Base44” 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 MCP connections in Base44
Open the account settings via your profile icon and choose “MCP connections”. Click “Add custom MCP”.
Enter address and header
Give it a name and paste the server address. Under authentication, choose “Custom header”. Enter “Authorization” as the header name and, as the value, “Bearer ” followed by your connection key. The exact format is shown below.
Test the connection
Confirm with “Test & add”. Base44 checks the connection right away. Then ask the editor chat for your open growResonance recommendations; in growResonance, the Base44 card shows a timestamp under “Last used”.

Server address

https://www.growresonance.ai/api/mcp

Header: name and value (replace the key)

Name:   Authorization
Value:  Bearer grvibe_YOUR_CONNECTION_KEY

Note: There is exactly one space between “Bearer” and the key. “Bearer” starts with a capital B. The key itself always starts with “grvibe_”. If that is not in the field, something was cut off while copying.

Important: Treat the connection key like a password. Anyone who has it can read the data of your workspace. Only enter it in the platform’s connector settings, never in your project’s source code and never in a chat prompt.

What you can do with the connection

With the connection, Base44 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. Base44 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.

Note: growResonance does not change anything on your website through this connection. We do not write to any repository, do not publish to any CMS and do not call any third-party page. What happens with the data that is read is decided only by Base44 in your own environment, with your permissions.

Note: In Base44, MCP connections only work in the editor chat while you build your project, not at runtime of the finished app. Your users do not see any of it.

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 app.”
“Get the FAQ schema from the recommendation and add it to the right page.”
“Show me the critical issues from my last Technical Audit.”

Note: A connection always applies to exactly one workspace. If you are an agency managing several clients, set up the connection for each workspace separately. The AI then only sees the data of that client.

Base44: set up a custom MCP (official documentation) – Base44’s menus, in the original.

Troubleshooting and FAQ

“Test & add” fails.

Check the header value character by character: it must read “Bearer ” (capital B, one space) followed by the full key with the prefix “grvibe_”. A missing space, a doubled “Bearer Bearer” or a cut-off key are the three most common causes.

I don’t see “MCP connections” in my account.

Custom MCP connections require at least the Builder plan on Base44. On lower plans the menu item does not exist. This only concerns your Base44 account; your growResonance plan plays no role here.

Can my finished app use the connection?

No. Base44 only uses MCP connections in the editor chat, that is, while building. The published app does not talk to growResonance, and your users do not see any data from your workspace.

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.