About MCP Server for Feedly API
This TypeScript MCP server exposes selected Feedly API endpoints for searching and retrieving articles and NLP entity information. It supports a discovery flow from entity lookup to article collection.
Key features
- 01Search Feedly content
- 02Collect articles from streams
- 03Look up entity details
- 04Autocomplete entity IDs
Use cases
- 01Discover articles about a topic or company
- 02Retrieve full articles from a feed or board
- 03Find entity IDs before searching
- 04Research technology trends
MCP support
Exposes four Feedly API operations as tools for MCP-aware language models. It communicates with clients over stdio and requires a FEEDLY_TOKEN to call the Feedly API.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP Server for Feedly API
This repository contains a minimal typescript-sdk server that exposes selected Feedly API endpoints as MCP tools. The server provides the following tools:
feedly.searchfeedly.collectfeedly.entity_lookupfeedly.autocomplete
These tools make it possible for MCP-aware language models to search and retrieve articles or NLP entity information from Feedly.
Complete Feedly Workflow
The tools work together in a typical discovery loop:
- Entity discovery – use
feedly.autocompleteto find IDs for relevant topics or companies. - Content search – call
feedly.searchwith those IDs to locate articles and discover stream IDs. - Stream collection – pass a stream ID to
feedly.collectto retrieve full articles from a feed or board. - Entity details – fetch additional information about any entity using
feedly.entity_lookup.
Key Concepts
- Entities – topics, companies, people or technologies identified by Feedly IDs.
- Streams – RSS feeds, user categories or publication buckets.
- Salience – choose
mentionoraboutto control how prominently an entity appears in results. - Sources – which streams to search in (defaults to all topics).
Common entity ID patterns include nlp/f/topic/xxxx for topics and feed/http://... for RSS feeds.
Troubleshooting
- Ensure
FEEDLY_TOKENis exported so the server can call the Feedly API. - Use
feedly.autocompletefirst to confirm entity IDs. - Some streams may not support direct collection; discover stream IDs via
feedly.search. - Use pagination tokens and the
countparameter to stay within Feedly rate limits.
Example Workflows
The comments in server.ts contain full examples such as tracking AI in healthcare, running company research and analyzing technology trends.
Setup
- Install dependencies using npm:
npm install
- Export your Feedly authentication token so the server can call the Feedly API:
export FEEDLY_TOKEN=YOUR_TOKEN_HERE
Running the server
Run the server over stdio so there is no network port to configure. Simply start it with:
npx ts-node server.ts
The process stays alive and communicates with clients via its standard input and output streams.
Using with Claude Desktop
To connect Claude Desktop directly to this server, open File > Settings > Developer > Edit Config and
create or update claude_desktop_config.json with an entry like:
{
"mcpServers": {
"feedly": {
"command": "npx",
"args": [
"ts-node",
"/path/to/mcp_server_feedly/server.ts"
],
"env": {
"FEEDLY_TOKEN": "YOUR_TOKEN_HERE"
}
}
}
}
Claude Desktop communicates with the server over stdio, so there is no URL to configure. command and args tell the app how to start it. Replace the path with the location of server.ts on your system and set FEEDLY_TOKEN to your Feedly token.
You can copy claude_desktop_config.example.json from this repository as a starting point.
Running tests
Install the Python dependencies and run the test suite:
pip install -r requirements.txt
FEEDLY_TOKEN=xxxx pytest -q
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.