Skip to main content
Glama
README.md
# Inoreader MCP server

Connect Inoreader to ChatGPT, Claude and other AI agents through Cotlet.dev. Read and organize articles, manage feeds and draft rules in your signed-in Inoreader account. Creating a rule asks for approval by default.

## What you can ask

> Star what matters in today's unread.

> Search my feeds and tag the best articles.

> File new feeds into folders.

## Connect in 2 minutes

Get your API key at https://cotlet.dev/app and export it as `COTLET_API_KEY`.

### ChatGPT

Settings → Apps → add connector URL `https://cotlet.dev/mcp/v1/connect`, then sign in with Cotlet.dev. No API key needed.

### Claude Code

```bash
claude mcp add --transport http cotlet https://cotlet.dev/mcp/v1 --header "Authorization: Bearer $COTLET_API_KEY"
```

### Cursor

Copy `.cursor/mcp.json` from this repo into your project:

```json
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

## Run it locally (stdio)

This repo is a real MCP server. It speaks MCP over stdio, lists its Inoreader tools without any key, and forwards every tool call to the hosted Cotlet.dev server. The hosted URL above stays the recommended way. Use this when your client only starts local servers.

Run the included Python module with Python 3.10 or later:

```bash
python3 inoreader_agent.py serve
```

Or with Docker:

```bash
docker build -t inoreader-mcp .
docker run -i --rm -e COTLET_API_KEY inoreader-mcp
```

Tools: `inoreader_guide`, `inoreader_status`, `inoreader_open`, `inoreader_read`, `inoreader_click`, `inoreader_type`, `inoreader_close`. Without `COTLET_API_KEY` a tool call answers: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app".

## Command line

Python 3.10+, with no third-party runtime dependencies. Clone this repository and run:

```bash
export COTLET_API_KEY="your-key"
python3 inoreader_agent.py connect   # ready config for Claude Code, Cursor, ChatGPT
python3 inoreader_agent.py status    # is Inoreader ready in your Cotlet.dev account
python3 inoreader_agent.py guide     # Inoreader screens and sign-in link
python3 inoreader_agent.py read      # open Inoreader, read the page, close the browser
python3 inoreader_agent.py tools     # list Cotlet.dev tools
python3 inoreader_agent.py serve     # start the stdio MCP server (same as no argument)
```

## Questions from Inoreader users

**Do I need an Inoreader developer app?**

No. Sign in to Inoreader in your Cotlet.dev Cloud Browser and enable it for agents.

**Do I need the Pro plan?**

Reading, starring, tagging and managing feeds work on Free within its plan limits. Rules and search across public articles require Pro.

**Is Cotlet affiliated with Inoreader?**

No. Cotlet.dev is independent and not affiliated with Inoreader or Innologica.

## Learn more

- [Inoreader integration and hosted tools](https://cotlet.dev/integrations/inoreader-api-mcp-server)

---

More: https://cotlet.dev/integrations/inoreader-api-mcp-server?utm_source=github&utm_medium=readme&utm_campaign=inoreader

Request access: https://cotlet.dev/signup?app=inoreader&utm_source=github&utm_medium=readme&utm_campaign=inoreader

## Workflows on the hosted integration

The live integration page documents these 16 operations:

- `get_unread_counts`
- `list_articles`
- `search_articles`
- `mark_as_read`
- `star_article`
- `tag_article`
- `list_subscriptions`
- `list_folders`
- `add_feed`
- `move_feed`
- `unsubscribe_feed`
- `list_rules`
- `create_rule`
- `list_annotations`
- `list_filters`
- `list_monitoring_feeds`

The local stdio adapter exposes seven browser helpers listed above. These helpers forward to Cotlet.dev; the workflow operations are documented on the hosted integration page.

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues