[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Feedly MCP tools

> The Feedly MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/feedly

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Feedly has 14 operations on the Cotlet MCP server, in feedly_read and feedly_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `feedly_read`, `feedly_write`
- Connects with: Your own Feedly account. Team Feeds and Team Boards appear if your account has them (Team Feeds are Enterprise only). You sign in in your own browser and keep your 2-step verification.
- Integration page: https://cotlet.dev/integrations/feedly-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_feeds`](https://cotlet.dev/docs/mcp/feedly/list_feeds.md) | Your Feeds with the sources in each and the unread count. |
| [`list_articles`](https://cotlet.dev/docs/mcp/feedly/list_articles.md) | Articles in a Feed, source, Board or Read Later, newest first, with read state. |
| [`get_article`](https://cotlet.dev/docs/mcp/feedly/get_article.md) | Full article text with source, link, read state and the Boards it is saved in. |
| [`search_articles`](https://cotlet.dev/docs/mcp/feedly/search_articles.md) | Search article text in your Feeds, optionally inside one stream. |
| [`list_boards`](https://cotlet.dev/docs/mcp/feedly/list_boards.md) | Your Boards, personal and team, with the number of articles in each. |
| [`search_sources`](https://cotlet.dev/docs/mcp/feedly/search_sources.md) | Search Follow Sources for websites and feeds by topic, with followers and posting rate. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`save_to_board`](https://cotlet.dev/docs/mcp/feedly/save_to_board.md) (Confirm) | Save an article to a Board, the star icon in the reader. |
| [`add_url_to_board`](https://cotlet.dev/docs/mcp/feedly/add_url_to_board.md) (Confirm) | Add a web page or PDF that is not in your Feeds to a Board, with a note. |
| [`mark_articles_read`](https://cotlet.dev/docs/mcp/feedly/mark_articles_read.md) | Mark articles as read or unread, optionally hiding them from the list. |
| [`mark_all_read`](https://cotlet.dev/docs/mcp/feedly/mark_all_read.md) | Mark every article in a Feed or source as read, optionally only older ones. |
| [`save_for_later`](https://cotlet.dev/docs/mcp/feedly/save_for_later.md) | Add an article to Read Later, or remove it. |
| [`follow_source`](https://cotlet.dev/docs/mcp/feedly/follow_source.md) | Follow a source and add it to a Feed, creating the Feed if you name a new one. |
| [`unfollow_source`](https://cotlet.dev/docs/mcp/feedly/unfollow_source.md) | Stop following a source. |
| [`move_source`](https://cotlet.dev/docs/mcp/feedly/move_source.md) | Move a source you follow from one Feed to another. |

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.