Deploys a Model Context Protocol Server-Sent Events (SSE) deployment on Google Cloud Run with IAM authentication.
Authenticated Cloud Run MCP server exists for a simple reason — assistants are far more useful when they can act on Authenticated Cloud Run directly instead of describing what you should do. Deploys a Model Context Protocol Server-Sent Events (SSE) deployment on Google Cloud Run with IAM authentication.
At the moment (03/04/2024) MCP is still addressing Authentication and Authorization. They plan to complete this in H1 2025. The issue is, I want to share my MCP server with my team NOW. So here we are. The only immediate answer to use a SSE MCP server in Cursor, etc.. right now is a network layer based solution (e.g., a proxy). Basic auth, api keys, forget about it.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Authenticated Cloud Run is connected, these are the calls the assistant has available:
PROJECT_ID — Your Google Cloud project IDREGION — Your preferred GCP regionSERVICE_ACCOUNT_EMAIL — The service account email with appropriate permissionsYou will need one environment variable: PROJECT_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Authenticated Cloud Run's toolset — PROJECT_ID, REGION, SERVICE_ACCOUNT_EMAIL — is a fair guide to whether it matches your workflow. It is maintained by the-freetech-company; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Authenticated Cloud Run's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| PROJECT_ID | Your Google Cloud project ID |
| REGION | Your preferred GCP region |
| SERVICE_ACCOUNT_EMAIL | The service account email with appropriate permissions |
{
"mcpServers": {
"authenticated-cloud-run": {
"command": "npx",
"args": ["-y", "ts-node"],
"env": {
"PROJECT_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| PROJECT_ID | Configuration value read at startup. | Optional |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.