spark-agent-tools — MCP servers for Gemini Spark
A monorepo of Model Context Protocol (MCP) servers designed to connect to Gemini Spark as custom Connected Apps, each with a complete OAuth 2.1 authorization layer baked in.
Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
A monorepo of Model Context Protocol (MCP) servers designed to connect to Gemini Spark as custom Connected Apps, each with a complete OAuth 2.1 authorization layer baked in.
Hello-world MCP servers for Gemini Spark: full OAuth 2.1 scaffolding (RFC 9728 + 8414 + 7591 + 7636 PKCE) in self-contained Go binaries, deployable to Cloud Run in one command.
Gemini Spark is a personal AI agent in the Gemini app that can automate workflows using built-in and custom Connected Apps — the latter are hosted MCP servers you point Spark at. (overview · connected apps · add a custom app)
Prerequisites: Go 1.25+. To deploy, also the gcloud CLI and a GCP project
with billing.
Run the hello-world server locally with auth bypassed — the fastest way to see
it work:
cd hello-world
make run-dev # serves on :8080, AUTH_BYPASS=true
Watch the OAuth discovery chain respond:
curl -s localhost:8080/.well-known/oauth-protected-resource | jq
curl -s localhost:8080/.well-known/oauth-authorization-server | jq
curl -s -X POST localhost:8080/api/oauth/register \
-H 'content-type: application/json' \
-d '{"redirect_uris":["https://example.com/cb"],"client_name":"demo"}' | jq
Run the full test suite (it walks DCR → authorize → PKCE token → protected call in-process):
make test
To enforce the real OAuth/JWT layer instead of bypassing it:
JWT_SIGNING_KEY=$(openssl rand -hex 32) make run
cd hello-world
cp .env.example .env # set GCP_PROJECT
make deploy # builds from source, prints your Service URL
Paste the printed Service URL into Gemini Spark → Connected Apps. The full
click-through and a troubleshooting table are in
docs/connecting-spark.md.
See also: Google Cloud's official tutorial Build and deploy a remote MCP server on Cloud Run shows the same deployment pattern in Python using FastMCP and Cloud Run's built-in IAM auth. That approach works well for developer tooling. This repo adds the OAuth 2.1 discovery + authorization chain (RFC 9728 / 8414 / 7591 / 7636) that Gemini Spark specifically requires on top of it.
When you paste a plain MCP URL into Spark, you may hit:
"This server does not support automatic registration. To connect, enter your own OAuth client ID and secret below."
…and the server logs fill with 404s. That's because Spark expects a
standards-compliant OAuth 2.1 resource server, specifically:
The shared pkg/mcpauth package implements all four. Each tool subdirectory
wires it in with a handful of lines so tool code is purely tool logic. See
docs/oauth-deep-dive.md for the full story of why
each piece is required.
go.mod single Go module for the whole repo
pkg/mcpauth/ shared OAuth 2.1 package (RFC 9728/8414/7591/7636)
mcpauth.go Store interface, AuthServer, Mount, RequireBearer
mcpauth_test.go full-flow tests (DCR, PKCE, JWT, discovery)
hello-world/ MCP server: one "echo" tool, complete auth scaffolding
main.go HTTP wiring: routes, middleware, startup
mcp.go the echo tool + SSE/Streamable-HTTP multiplexer
Dockerfile distroless multi-stage build (context = repo root)
scripts/deploy.sh one-command Cloud Run deploy
Makefile developer targets (run, run-dev, test, build, deploy)
.env.example config template; copy to hello-world/.env
omi-bridge/ OAuth 2.1 bridge proxy for Omi's hosted MCP server
main.go HTTP wiring: routes, passphrase consent, middleware
mcp.go proxy handler + SSE/Streamable-HTTP forwarding
cloudbuild.yaml Cloud Build config for repo-root context build
scripts/deploy.sh one-command Cloud Run deploy script
Makefile developer targets
.env.example config template; copy to omi-bridge/.env
docs/
TUTORIAL.md build-it-yourself walkthrough
connecting-spark.md connect from the Spark UI + troubleshooting table
oauth-deep-dive.md why RFC 9728/8414/7591/7636, with request traces
LESSONS_LEARNED.md field notes from live Spark connections
omi-mcp-tutorial.md tutorial: connecting Omi to Spark + omi-bridge guide
architecture.webp the discovery + auth flow, visualized
To add a new tool: create a subdirectory (e.g. calendar-tool/), add
main.go + mcp.go, import pkg/mcpauth, and call mcpauth.Mount(mux, authz).
hello-world keeps two things minimal so it runs anywhere with no external
dependencies. Both are flagged in pkg/mcpauth and in
docs/oauth-deep-dive.md,
and both need changing for a real deployment:
mcpauth.Store implementation for
production.mcpauth.Options.ResolveSubject to authenticate the user with
your IdP before issuing a code.For a production-grade reference that does both — persistent Firestore storage, a Firebase consent SPA, per-user scopes, and the same RFC stack serving two protocols (MCP + A2A) — see the eldamo-server project this tutorial was distilled from.
Apache 2.0 — see LICENSE.
Hello-world MCP servers for Gemini Spark: full OAuth 2.1 scaffolding (RFC 9728 + 8414 + 7591 + 7636 PKCE) in self-contained Go binaries, deployable to Cloud Run in one command.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Spark Agent Tools roda localmente via stdio.
Última verificação: 2026-10-28. Hello-world MCP servers for Gemini Spark: full OAuth 2.1 scaffolding (RFC 9728 + 8414 + 7591 + 7636 PKCE) in self-contained Go binaries, deployable to Cloud Run in one command.