mcpbeat Sign in

Google Discover MCP Server and API by Cotlet

answering

Google Discover MCP Server and API by Cotlet is answering right now. Last checked 1 min ago. It exposes 30 tools. Last commit 5 Nov 2026.

Google Discover MCP server: read Discover feed, check domain in feed.

Uptime history 14 hours of history · worst hour 88%
14 hours agonow
99.0%
Uptime 24h
101 of 102 checks
30
Tools
read from the server
233 ms
Response time
average over 24h
5
Stars
last commit 5 Nov 2026

Google Discover MCP Server and API by Cotlet does not always answer

Over the last week it answered 99.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add google-discover --transport http https://cotlet.dev/mcp/v1/google-discover/connect
Settings → Connectors → Add custom connector, then paste this address
https://cotlet.dev/mcp/v1/google-discover/connect
~/.codex/config.toml
[mcp_servers.google-discover]
url = "https://cotlet.dev/mcp/v1/google-discover/connect"
.cursor/mcp.json
{
  "mcpServers": {
    "google-discover": {
      "url": "https://cotlet.dev/mcp/v1/google-discover/connect"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "google-discover": {
      "type": "http",
      "url": "https://cotlet.dev/mcp/v1/google-discover/connect"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 30

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

cotlet
cotlet_app_guide
How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Google Discover it covers these actions: Read Discover feed, Check domain in feed.
cotlet_apps
The apps of the user's workspace and whether each works now: the app account in the user's Cloud Browser (connected, signed out, signed in but not connected), and the one step the user has to take, with the console link. Free. Needs the user's Cotlet API key or sign-in.
cotlet_browser_click
Clicks element `element`, or point `x`, `y` of the screenshot; `double` double-clicks, `button: right` right-clicks. Answers the page after it: the elements and text in view, with the same numbers. Says when nothing changed. A link that would open a new tab opens in this one. Buttons that pay or buy, and sign-in and account pages, are refused.
cotlet_browser_close
Ends the browser session when the task is done: the browser keeps its cookies and sleeps, and the per-minute charge stops. Answers the session's minutes and credits.
cotlet_browser_download
Gets the file that clicking `element` (a download link or button) or opening `url` starts: answers its name, type, size and a link valid 15 minutes; CSV, JSON and other text files also as text.
cotlet_browser_drag
Drags from one element or point to another: a card between columns, a piece on a board, a slider's handle. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_evaluate
Runs a JavaScript function body on the page and answers what it returns, as JSON. Use it to extract data the page holds (a table, a list, attributes); act with the other tools. It cannot send requests, click, submit, or read cookies or storage; a filled field's value reads [hidden by Cotlet]. Example: return [...document.querySelectorAll('h2')].map(h => h.innerText)
cotlet_browser_fill_form
Fills several fields in one step: text fields take text, drop-downs an option's label, checkboxes, radios and switches true or false. Stops at the first field that fails and names those filled. Does not send the form: click its button after. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_find
Finds `text` on the whole current page, frames included: the elements whose label holds it, with their numbers, and each line of text that holds it. Use it instead of reading or scrolling a long page for one thing.
cotlet_browser_hover
Rests the pointer on an element or a point, to open a hover menu, a tooltip or a preview. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_navigate
Opens `url` in the current tab, or goes `history` back or forward. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_open
Starts the user's Google Discover Cloud Browser (a real Chrome on Cotlet, signed in to Google Discover as the user; use it for what the Google Discover tools do not cover) and opens `url`. Call it first. Only Google Discover pages open. Answers the page after it: the elements and text in view, with the same numbers. In Google Discover it serves these actions: Read Discover feed, Check domain in feed.
cotlet_browser_press
Presses a key on the focused element: Enter to send, Tab to the next field, Escape to close a pop-up, arrows in a list or slider, or one character (a site's shortcut). Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_read
The whole current page: its text (up to 20,000 characters) and a numbered list of its links, buttons, fields and other controls, open dialogs first. Use it on a new page or when a step's answer is not enough; `element` reads only inside one element (a dialog, a form, a list). Never returns field values, cookies or storage.
cotlet_browser_screenshot
A JPEG of the visible part of the page. Use it for boards, canvases, maps, charts and layout that the text does not show, then click or drag by `x`, `y` of the image.
cotlet_browser_scroll
Scrolls with the mouse wheel: `down` or `up` by `screens`, to `top` or `bottom`, until `element` is in view, or inside a panel or list (`inside`). Content that loads on scroll appears. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_select
Chooses `option` (its label as listed, or its value) in drop-down `element`. For a home-made drop-down, click it, then click the option. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_type
Types `text` into field `element`, replacing what it held; `submit` presses Enter after it. For several fields use fill_form. Without `element` the text goes where the focus is, as a person types after clicking: for spreadsheet cells and editors that read does not number (Google Sheets, Docs), click the place first; there a tab in `text` presses Tab and a line break Enter, so one call fills a table. Answers the page after it: the elements and text in view, with the same numbers. Password, card and one-time code fields are refused: the user types them.
cotlet_browser_upload
Puts files into file field or upload button `element`: each file is {"url": "https://..."} or {"file_id": "..."} of a file uploaded to Cotlet; up to 10 files, 20 MB each. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_browser_wait
Waits until `text` shows on the page (at most `seconds`, default 5, up to 20), or just `seconds`: for results that load slowly. Says whether the text appeared. Answers the page after it: the elements and text in view, with the same numbers.
cotlet_get_call
Status of an earlier Cotlet call, by its call_id: pending (waits for the owner's approval in the Cotlet console), approved, running, success, rejected, expired, blocked or failed. For a call that answered with status pending or running.
cotlet_report_issue
Sends a report to the Cotlet team: a tool that failed or returned wrong data, an error you could not get past, or a step the browser could not do, with the page, the step and what you saw. A missing dedicated tool is not a problem to report: do the task in the browser. A feature the user asks for goes as feature_request. A report promises nothing: tell the user it was sent, never that something will be built or fixed, or when. The report carries the error text and call_id when there is one, never passwords or tokens. Needs the user's Cotlet API key or sign-in.
cotlet_request_apps
Requests access to apps for the user's workspace, as Request access in the console: every app is granted at once. Not needed to work in an app: the user's AI works in any web app in their Web browser with cotlet_app_guide. An app with dedicated tools gets them after the user signs in to it in their Cloud Browser. Access says nothing about whether a task works there: check that in the browser. Takes app slugs as listed at https://cotlet.dev/api/v1/apps. Free. Needs the user's Cotlet API key or sign-in.
cotlet_upload_file
Returns a one-time upload_url and a file_id for a local file (an image for a post, an attachment). The file is sent to upload_url with an HTTP PUT; an argument that takes a file accepts {"file_id": "..."}. Up to 25 MB, the URL works once. Free. Needs the user's Cotlet API key or sign-in.
cotlet_whoami
The Cotlet account this connection acts as: email, workspace, access status, the API key or OAuth client in use with its scope, the apps the workspace may call and its credit balance. Free. Needs the user's Cotlet API key or sign-in.
google
google_discover_check_domain_in_feed
Check domain in feed in the user's own Google Discover account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Discover step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Discover Cloud Browser. Google Discover's official API: Google Discover has no API for the feed (checked 25 Oct 2026).
google_discover_read_discover_feed
Read Discover feed in the user's own Google Discover account from ChatGPT, Claude or any AI agent. Returns how to do it in Google Discover step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Google Discover Cloud Browser. Google Discover's official API: Google Discover has no API for the feed (checked 25 Oct 2026).
collect
collect_discover_cards
Up to 300 different cards Discover shows in a country, from many reads, with how often each appeared. One read of the Discover feed holds about 31 cards, and each read draws them from a larger pool. This tool reads the feed of the country many times in parallel, each time from another home IP there, until it has the number of different cards asked for or the pool runs dry, and returns them at once. seen_in says in how many reads a card appeared (a card in most reads is the core of the feed, one seen once is rare) and best_position its highest place. Cards come most often seen first. complete is false when the feed held fewer different cards than asked for in the time of one call. A call takes up to about 70 seconds and costs more credits than one read, because it makes many.
discover
get_discover_feed
The cards Google Discover shows right now in a country, in feed order, with no Google account. Returns the Discover feed Chrome for Android shows on its New Tab page to someone who is not signed in to Google, read from a home IP in the country asked for: position, title, publisher, URL, domain, article or video, age as the card shows it, and the card image. It is the default feed of that country and language, not anyone's personal feed and not data from a panel of users. One read holds about 30 cards; the feed changes over the day, and a read is reused for up to 15 minutes per country and language.
domain
check_domain_in_feed
Whether cards from a domain are in a country's Discover feed now, and at which positions. Reads the same feed as get_discover_feed (signed out, from a home IP in the country) and keeps the cards whose link is on the domain or one of its subdomains. in_feed is false when none is there right now; feed_size says how many cards the feed held. Run it on a schedule to see when a story enters and leaves.

Endpoints

URLTransportStateLatencyChecked
https://cotlet.dev/mcp/v1/google-discover/connect streamable-http sign-in 307 ms 1 min ago
https://cotlet.dev/mcp/v1/google-discover streamable-http answering 413 ms 1 min ago

Alternatives to Google Discover MCP Server and API by Cotlet

same job, measured the same way
Google Docs MCP
by a1-x-tech

MCP server for the Google Docs API: read and edit documents, styles, tables, images, comments.

416 installs/wk local only
Google Search Console MCP Server and API by Cotlet
by cotlet

Google Search Console MCP server: request indexing, request URL removal, add user to property.

32 tools answering
Google Sheets MCP
by a1-x-tech

MCP server for the Google Sheets API: read and write ranges, sheets, formatting, charts, sharing.

417 installs/wk local only
Google Forms MCP
by a1-x-tech

MCP server for the Google Forms API: create forms, manage questions, read responses and watches.

495 installs/wk local only
Google Tasks MCP
by a1-x-tech

MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.

393 installs/wk local only
MCP Serp
by acedatacloud

MCP server for Google search results via SERP API

1 004 installs/wk answering
Google Chat MCP
by a1-x-tech

MCP server for the Google Chat API: spaces, messages, threads, reactions and memberships.

437 installs/wk local only
MCP Gsheets
by freema

MCP server for Google Sheets API — read, write, format, batch operations.

5 127 installs/wk local only

Google Discover MCP Server and API by Cotlet — questions

Answers built from our own checks of this server.

What can Google Discover MCP Server and API by Cotlet do?
It exposes 30 tools, read directly from the server on our last check. Among them: check_domain_in_feed, collect_discover_cards, cotlet_app_guide, cotlet_apps, cotlet_browser_click, cotlet_browser_close and 24 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Google Discover MCP Server and API by Cotlet mostly used for?
Its tools cluster around cotlet and google. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Google Discover MCP Server and API by Cotlet working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 101 of 102 checks got a reply (99.0%), average response time 233 ms. The bar chart above shows every period we have measured.
How do I connect Google Discover MCP Server and API by Cotlet?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Google Discover MCP Server and API by Cotlet?
No API key is involved. Google Discover MCP Server and API by Cotlet answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Google Discover MCP Server and API by Cotlet?
It answers our handshake in 233 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Google Discover MCP Server and API by Cotlet open source?
We cannot say either way: written in Python and 5 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.