Home › Platforms › Gemini Connected Apps
Gemini Connected Apps
The Gemini app adds a custom MCP server by URL in Connected Apps. Named apps on the public list are not labeled as MCP.
What the docs say
Gemini Apps Help says you add a custom app with its Model Context Protocol (MCP) server URL in Connected Apps on the Gemini web app. The page says the server must follow the standard MCP specifications. A server that does not support Dynamic Client Registration needs credentials under Advanced features. Custom apps are connected in the Gemini web app and then available in the Gemini mobile app and at gemini.google.com. The page does not name stdio, SSE, or Streamable HTTP. The public Connected Apps table names many apps and does not label those apps as MCP servers, so this page does not list them. Google's October 28, 2026 blog says developers integrate with a cloud-hosted MCP server or Android MCP using the AppFunctions APIs. That post names partner Connected Apps and does not say each partner app is an MCP server. The developer guide is at developers.google.com/connected-apps/mcp.
Auth. The custom-app page says a server without Dynamic Client Registration needs credentials entered under Advanced features. It says Gemini requires manual confirmation for write actions. It does not publish an OAuth field list.
Limits from the docs
- Custom apps require age 18 or over, a personal Google Account, the US, English, and Keep Activity on.
- Work or school Google Accounts cannot connect a custom app.
- Custom apps are connected in the Gemini web app. The help page says they are then available in the Gemini mobile app and at gemini.google.com.
- The help page says Google does not control, monitor, or secure third-party MCP servers.
Setup
- On a computer, open gemini.google.com, then Settings and Connected Apps.
- Under Custom apps, add a custom app and enter its MCP server URL.
- If the server does not support Dynamic Client Registration, open Advanced features and enter credentials.
Sources
- Connect and manage custom apps for Gemini Apps Checked 2026-11-03
- Use and manage Connected Apps in Gemini Checked 2026-11-03
- Connected Apps Platform launch, October 28, 2026 Checked 2026-11-03
- Connected Apps Platform MCP server developer guide Checked 2026-11-03
Compatibility rule
A listing is included when its directory transport token is one this platform's docs describe. The token is SSE when the transport label contains “sse”; otherwise HTTP when the label contains “http” or the listing has a hosted remote endpoint; otherwise stdio when the label contains “stdio”; otherwise undeclared. Undeclared listings are left out. This is a transport match, not a connection test. MCPwell has not run these servers inside this platform.
The docs checked for this platform do not name a configurable MCP transport.
The docs checked here describe a custom MCP server URL and do not name stdio, SSE, or Streamable HTTP, so no directory listing is counted as compatible. Named Connected Apps from the public table are not marked officially listed. This is not a connection test.
Officially listed is a separate mark. It is used only when this platform's own directory or connector gallery names that server and the name matches one listing in this directory. A sentence in a setup example is not a gallery listing. The mark is not a connection test.
MCP servers (0)
Paid listings (Sponsored, then Featured) appear first in every list, marked Advertisement. Organic listings follow, sorted by GitHub stars. Sorted by GitHub stars as of 2026-10-17. Servers with no public GitHub repo follow, in alphabetical order.
First-party connectors
The public Connected Apps table is not an MCP gallery. This page does not copy those app names into a connector list.