Same problem for me, i cannot generate API key to use Stitch as MCP.
Is it a global problem?
Same issue here. Failed at first, but then tried a couple more times and don’t get a failure notice, but no keys show up.
Im experiencing the same thing. Is there a setting that we need to enable in google cloud console? I thought it was a timing thing, but 48 hrs and still the same issue persists!
Hey @ridwan47 @rambunctiousme88 @Casey @vector11 sorry for the trouble. I have escalated this to the team, and we will have a fix for this soon. In the meantime, could you please try clearing your cache for Stitch and logging back in?
Same Issue here, tried Incognito, tried clearing cache, nothing worked
@RISHABH_CHAUHAN have same issure, can not generate an api key
Hi @guangyi_qin, are you able to create the key now? Please let us know once you’ve confirmed. The team has been working on this, and we are seeing a significant decrease in reports regarding this issue.
Hey @naveedhassan, our systems show that API key generation is currently functional. Could you please give it another try and confirm if it’s working for you now?
hey @RISHABH_CHAUHAN, still doesnt work, but i figured a different way to access stitch using a key generated from my Google Cloud Project
I tried all of those and it did not work. However today, it started working. This is the same machine. I believe there was an issue with the api generation functionality, considering no changes were done.
Thanks for confirming, @rambunctiousme88. The team has addressed the underlying problem, and everything is working smoothly on our end now. Please don’t hesitate to reach out if you encounter any other API key issues down the road.
Still not able to create a key. Says it created successfully but doesnt show up
Hey @Bishal, could you please try generating a new one using a different account for the time being? Thanks!
Hey @RISHABH_CHAUHAN , I just wanted to add my name to the list of people with the same problem. Thanks for helping us out here.
The same problem is happening for me too. This is quite devastating as Stitch forms part of a critical area in my current business. Hope y’all can fix this soon!
I checked the Chrome DevTools console. I hope this helps with debugging:
installHook.js:1 [Stitch] RPC failed: code=7 message= httpStatus=undefined
installHook.js:1 Error: Zc`7`
at new _.BP (m=oxe1Cc:193:115)
at _.hR.G (m=oxe1Cc:199:297)
at m=oxe1Cc:183:213
at _.zL (m=oxe1Cc:123:112)
at uQ (m=oxe1Cc:183:131)
at b.jm (m=oxe1Cc:184:407)
at TN (m=oxe1Cc:51:129)
at DO (m=oxe1Cc:64:421)
at zN.J (m=oxe1Cc:63:86)
at zN.wa (m=oxe1Cc:61:221)
util-zQmNWgkH.js:178 Failed to create API key: Error: Failed to create API key. [object Object]
at Fo (util-zQmNWgkH.js:178:14014)
at createApiKey (McpSetupPage-hEhMocUQ.js:9:957)
at async _ (McpSetupPage-hEhMocUQ.js:9:1549)
Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestors 'self'". The violation has been logged, but no further action has been taken.
installHook.js:1 [Stitch] RPC failed: code=7 message= httpStatus=undefined
installHook.js:1 Error: Zc`7`
at new _.BP (m=oxe1Cc:193:115)
at _.hR.G (m=oxe1Cc:199:297)
at m=oxe1Cc:183:213
at _.zL (m=oxe1Cc:123:112)
at uQ (m=oxe1Cc:183:131)
at b.jm (m=oxe1Cc:184:407)
at TN (m=oxe1Cc:51:129)
at DO (m=oxe1Cc:64:421)
at zN.J (m=oxe1Cc:63:86)
at zN.wa (m=oxe1Cc:61:221)
util-zQmNWgkH.js:178 Error: Failed to create API key. [object Object]
at Fo (util-zQmNWgkH.js:178:14014)
at createApiKey (McpSetupPage-hEhMocUQ.js:9:957)
at async D (SettingsPage-B2keUEmX.js:1:3482)
Hey @Jakwakwa @k-tipp, thanks so much for providing these logs! The tool is working fine for us, but based on your logs, here are two factors that might be causing the failure:
- Your account may have been automatically flagged for security reasons if an API key was ever accidentally pasted into a prompt or left public on GitHub.
- If you are logged into multiple Google accounts in one Chrome profile, the auth script can mix up the active session tokens.
Please try these workarounds:
- Open Stitch in incognito mode, log in with the specific Google account, and try creating the key.
- Go to the GCP Console, select your project, and navigate to APIs & Services > Credentials.
Please try this and let me know if it works. I have already shared the logs with the team. Thanks!
Your account may have been automatically flagged for security reasons if an API key was ever accidentally pasted into a prompt or left public on GitHub.
That is actually possible in my case. Any suggestions on how to proceed?
Please try these workarounds:
Open Stitch in incognito mode, log in with the specific Google account, and try creating the key.
I tried this without any success, I also tried to generate a key using Firefox, which also didn’t work.
Go to the GCP Console, select your project, and navigate to APIs & Services > Credentials.
I did that and could successfully create an API-Key. But using that key for the MCP-Server in Antigravity does not work.
Logs and Attachments:
Chrome - DevTools - Console after trying to generate a key:
-
Request 1
https://stitch.withgoogle.com/_/Nemo/data/batchexecute?rpcids=MUAiWe&source-path=%2Fsettings&bl=boq_pitchfork-nemo-ui_20260618.01_p0&f.sid=3372714673323977407&hl=de&_reqid=1043747&rt=c Request Method: POST Status Code: 200 OK-
Response
-
-
Request 2
https://stitch.withgoogle.com/_/Nemo/jserror?script=https%3A%2F%2Fstitch.withgoogle.com%2Fsettings&error=bd%60%3Ceye3-stackless%20title%3D%27Error%3A%20Failed%20to%20create%20API%20key.%20%5Bobject%20Object%5D%27%2F%3E%60Failed%20to%20create%20API%20key.%20%5Bobject%20Object%5D&line=Not%20available Request Method: POST Status Code: 204 No Content-
Payload
Error: Failed to create API key. [object Object] at Fo (https://app-companion-430619.appspot.com/assets/util.js:178:14014) at createApiKey (https://app-companion-430619.appspot.com/assets/McpSetupPage.js:9:957) at async D (https://app-companion-430619.appspot.com/assets/SettingsPage.js:1:3482) -
Response
-
Empty
-
-
Console:
m=oxe1Cc:589 [Stitch] RPC failed: code=7 message= httpStatus=undefined
L8 @ m=oxe1Cc:589
(anonymous) @ m=oxe1Cc:591
c @ m=_b:339
Promise.then
f @ m=_b:339
(anonymous) @ m=_b:339
tt @ m=_b:339
_.F @ m=_b:339
handle @ m=oxe1Cc:591
(anonymous) @ m=oxe1Cc:592
(anonymous) @ m=_b:339
tt @ m=_b:339
_.F @ m=_b:339
P8 @ m=oxe1Cc:592
eba @ m=oxe1Cc:603
(anonymous) @ m=oxe1Cc:764
(anonymous) @ m=_b:339
tt @ m=_b:339
_.F @ m=_b:339
Va @ m=oxe1Cc:764
(anonymous) @ m=oxe1Cc:750
(anonymous) @ m=_b:339
tt @ m=_b:339
_.F @ m=_b:339
Bba @ m=oxe1Cc:748
(anonymous) @ m=oxe1Cc:754
Vm @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:203
(anonymous) @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:203
ll @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:182
ul @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:182
Pk @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:183
Vk.MK @ cb=gapi.loaded_0?le=scs,fedcm_migration_mod:176
m=oxe1Cc:750 Error: Zc`7`
at new _.DP (m=oxe1Cc:193:115)
at _.jR.G (m=oxe1Cc:199:297)
at m=oxe1Cc:183:213
at _.BL (m=oxe1Cc:123:112)
at wQ (m=oxe1Cc:183:131)
at b.lm (m=oxe1Cc:184:407)
at VN (m=oxe1Cc:51:129)
at FO (m=oxe1Cc:64:421)
at BN.J (m=oxe1Cc:63:86)
at BN.wa (m=oxe1Cc:61:221)
util-zQmNWgkH.js:178 Error: Failed to create API key. [object Object]
at Fo (util-zQmNWgkH.js:178:14014)
at createApiKey (McpSetupPage-hEhMocUQ.js:9:957)
at async D (SettingsPage-B2keUEmX.js:1:3482)
Io.console.error @ util-zQmNWgkH.js:178
D @ SettingsPage-B2keUEmX.js:1
Antigravity
StitchMCP configuration as generated via the MCP Server Manager
"StitchMCP": {
"$typeName": "exa.cascade_plugins_pb.CascadePluginCommandTemplate",
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://stitch.googleapis.com/mcp",
"--header",
"X-Goog-Api-Key: [API_KEY]"
],
"env": {}
}
Kind regards
k-tipp
Hello! Same problem here.
Same error message. Already tried incognito mode without success. Tried on my mobile too, same error. 
SOLVED [1]
Thank you for the feedback. It turns out I was the culprit. I removed the Service Accounts by accident a couple of days ago, and when I eventually deciphered the issue, I realised I needed to hunt down a missing SA. Finding it and restoring the SA turned out to be the exact resolution in my case.
I’d like to flag a concern andI humbly request that GCP or, more so, Stitch Labs, make it abundantly clear that there is a GCP project automatically created when opening a Stitch account. Simply adding a clearly marked GCP project ID somewhere in the settings screen would make a huge difference IMO. This could have saved me, and potentially other idiots like me, many, MANY hours of highly stressful debugging. 
To be fair, SOLVED here within my specific use case. Please read through my original post to see if my resolution can be helpful too. ↩︎