Productivity & teams
Redmine
Issues, time entries and projects in your Redmine, from your agent.
12 endpoints
Feedly's API is Enterprise only and has no endpoint for Read Later or finding new sources. Sign in to Feedly once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.
Not affiliated with Feedly.
| What you need | Feedly's API | GitHub MCP server | Cotlet |
|---|---|---|---|
| Read Later, source discovery | No | Partly | Yes, 14 tools |
| Acts as you, signed in 24/7 | No | No | Yes, Cloud Browser |
| Fixed for you when Feedly changes | N/A | No | Yes, tested every 6h |
| Runs with your laptop off | N/A | No | Yes, hosted |
Checked Oct 17, 2026. Sources: Feedly API: Authorization · Feedly API: endpoint reference index · Feedly Help: Setting up the Feedly MCP server in Claude · Feedly triggers and actions on Zapier
AI agents connect over MCP, scripts call the REST API. Both reach the same 14 tools with one API key.
Add Cotlet to your agent once. Feedly and every other app you connect show up as its tools.
claude mcp add --transport http cotlet \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY" {
"mcpServers": {
"cotlet": {
"url": "https://cotlet.dev/mcp/v1",
"headers": {
"Authorization": "Bearer ${COTLET_API_KEY}"
}
}
}
} # ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY" Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.
Every tool is an endpoint under /api/v1/feedly with its own method and path, such as POST /api/v1/feedly/boards/{board_id}/url-to-boards, with the same API key. Our open-source repo has ready scripts to start from.
14 tools on your own Feedly account. Agents call them as operations of the MCP tools feedly_read and feedly_write; scripts call each one at its own REST endpoint, with the same inputs and answers.
| Tool | What it does | Access |
|---|---|---|
| list_feeds | Your Feeds with the sources in each and the unread count. | read |
| list_articles | Articles in a Feed, source, Board or Read Later, newest first, with read state. | read |
| get_article | Full article text with source, link, read state and the Boards it is saved in. | read |
| search_articles | Search article text in your Feeds, optionally inside one stream. | read |
| list_boards | Your Boards, personal and team, with the number of articles in each. | read |
| search_sources | Search Follow Sources for websites and feeds by topic, with followers and posting rate. | read |
| save_to_board | Save an article to a Board, the star icon in the reader. | writeasks first |
| add_url_to_board | Add a web page or PDF that is not in your Feeds to a Board, with a note. | writeasks first |
| mark_articles_read | Mark articles as read or unread, optionally hiding them from the list. | write |
| mark_all_read | Mark every article in a Feed or source as read, optionally only older ones. | write |
| save_for_later | Add an article to Read Later, or remove it. | write |
| follow_source | Follow a source and add it to a Feed, creating the Feed if you name a new one. | write |
| unfollow_source | Stop following a source. | write |
| move_source | Move a source you follow from one Feed to another. | write |
Scroll the table for all 14 tools.
You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.
One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Feedly is enabled for agents, so 20 calls a day come to 550 credits.
| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |
Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the Authorization: Bearer header.
Feedly has a REST API, but only Enterprise clients can create a token, and its documented endpoints are built around Threat Intelligence (checked 17 Oct 2026). Feedly's official MCP server, Feedly Threat Graph, queries threat intelligence and needs an Advanced or Enterprise account. Neither one lets an agent work your own feeds, Read Later and read state.
Sign up free, open Feedly under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.
No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 14 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.
Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Feedly yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Feedly sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.
Not on anything that reaches other people: save_to_board, add_url_to_board wait for your OK by default. You can switch that off per tool for scheduled runs.
mark_articles_read lowers the unread count for the source and Feed, the same as Feedly's Mark as read. With hide set to true it also removes the articles from the list until you reload. In a Team Feed, read status is per person, so teammates still see their own unread articles.
Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Feedly changes. Pick Cotlet if you want it hosted and kept working for you.
Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.
Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.
No. Cotlet is independent and not affiliated with Feedly.
Free 7-day trial with 2,000 credits, no card needed.
May we use Google Analytics to see which pages help people? It sets cookies only if you accept. No ads, and we never sell data. Cookie policy