Inoreader MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COTLET_API_KEY | Yes | Your Cotlet.dev API key. Get one at https://cotlet.dev/app. Passed as an environment variable, or as an "Authorization: Bearer $COTLET_API_KEY" header when using the hosted HTTP endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Inoreader through Cotlet.dev. Call inoreader_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inoreader_guideA | How to work in Inoreader (read articles, organize feeds and create rules): its screens and the sign-in link. Call this first. |
| inoreader_statusA | Check that your Cotlet.dev account and Inoreader are ready: account, credits and Inoreader connection. |
| inoreader_openA | Open a Inoreader page in your signed-in Cloud Browser (default https://www.inoreader.com) to work with read articles, organize feeds and create rules. |
| inoreader_readA | Read the current Inoreader page: its text and numbered buttons, links and fields. |
| inoreader_clickB | Click a numbered element on the current Inoreader page. |
| inoreader_typeA | Type text into a numbered field on the current Inoreader page. |
| inoreader_closeA | Close the Inoreader browser session when the work is done, so credits stop running. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clearly distinct role: session lifecycle (open/close), page interaction (read/click/type), and meta guidance (guide/status). There is no plausible confusion between reading a page and clicking an element, nor between the how-to guide and the account readiness check.
All tools share the inoreader_ snake_case prefix and a uniform single-word suffix style. Minor deviation: most suffixes are verbs (open, read, click, type, close) while guide and status are nouns, but the overall pattern remains predictable.
Seven tools is a well-scoped set for a browser-automation wrapper: exactly the primitives needed to drive a UI plus two meta tools. Nothing feels redundant or missing at the count level.
The core loop for driving Inoreader (open, read, click, type, close, plus guide and status) covers reading articles, organizing feeds, and creating rules through the UI. Minor gaps like explicit scroll, back/navigate, or wait utilities can be worked around via read/click on page elements.