How is this different from connecting Google Cloud Stitch MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Google Cloud Stitch MCP API changes?

We track the Google Cloud Stitch MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Google Cloud Stitch tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Google Cloud Stitch?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Google Cloud Stitch MCP server myself?

No. TrustGate connects to the Google Cloud Stitch MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Google Cloud Stitch directly.

Connect Google Cloud Stitch MCP to your AI agents, securely.

Q: Is Google Cloud Stitch MCP secure?

The server itself exposes 16 tools, and some of them can write to your Google Cloud Stitch account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Google Cloud Stitch.

One secured endpoint for every Google Cloud Stitch call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Google Cloud Stitch MCP now

What your agents can ask once Google Cloud Stitch MCP is connected.

Select the tools your AI agents can call

16 tools from the Google Cloud Stitch MCP schema.

Showing 16 tools

list_projectsreadLists the Stitch projects available to the authenticated user.
get_projectreadGets the details of a Stitch project.
create_projectwriteCreates a new Stitch project.
list_screensreadLists the screens in a Stitch project.
get_screenreadGets a generated screen, including its layout and components.
delete_projecthigh riskDeletes a specific Stitch project using its project name. The action cannot be undone.
download_filereadDownloads the content of a screen file: its HTML code or its screenshot.
generate_screen_from_textwriteGenerates a new screen within a project from a text prompt.
edit_screenswriteEdits existing screens within a project using a text prompt.
generate_variantswriteGenerates variants of existing screens within a project using a text prompt.
upload_design_mdwriteUploads a DESIGN.md file to a Stitch project, to create a design system from it.
create_design_systemwriteCreates a new design system for a project: the overall visual theme, style or branding, such as colour palette and typography.
create_design_system_from_design_mdwriteCreates a design system for a project from an uploaded DESIGN.md file and displays it in the UI.
update_design_systemwriteUpdates a design system for a project, changing the overall visual theme, style or branding.
list_design_systemsreadLists all design systems for a given project.
apply_design_systemwriteApplies a design system's design tokens (colours, fonts, shapes) to a list of screens.

What Google Cloud Stitch MCP exposes

Google Cloud Stitch MCP groups its 16 tools into 4 categories, each with a suggested starting policy.

All 16 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Generation	Generating screens from a text prompt, editing them and generating variants	Read / Write	Review generated designs before use
Projects & Screens	Project and screen listing, details, and project creation and deletion	Read / Write	Scope to intended projects; approve deletions, which cannot be undone
Export	Downloading a screen as HTML code or a screenshot	Read	Allow exports
Design Systems	Design systems for a project, created from settings or a DESIGN.md file, updated, listed and applied to screens	Read / Write	Applying a design system restyles existing screens; review before applying

Connect Google Cloud Stitch MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect Google Cloud Stitch
Find Google Cloud Stitch in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow Google Cloud Stitch MCP or block it. You allow the exact tools each agent can call, one by one.

Google Cloud Stitch MCP	16 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 16 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is Google Cloud Stitch MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	Google Cloud Stitch MCP16 documented tools.
Coding assistants	Connection & credentialsper user	Projects & Screens6 tools
Internal copilots	Tool access policiesdeny by default	Design Systems6 tools
Workflow automations	Request & response inspectioninline	Generation3 tools
Compatible MCP clients	Activity monitoringalerts and logs	All other tools1 tool