An MCP (Message Chain Protocol) server that fetches RSS feeds and shares them with LLMs.
An MCP (Message Chain Protocol) server that fetches RSS feeds and shares them with LLMs. Exposed over MCP by the mcp rss crawler mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
Everything the assistant can do here goes through one of these:
Bun — Firecrawl API keyPORT — Server port (default: 5556)FIRECRAWL_API_KEY — Firecrawl API keyDB_DIR — Database directory (default: ~/.mcp-rss-crawler)Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
You will need 4 environment variables: PORT, DB_DIR, FIRECRAWL_API_KEY, YOUR_FIRECRAWL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Rss Crawler's toolset — Bun, PORT, FIRECRAWL_API_KEY and 1 more — is a fair guide to whether it matches your workflow. It is maintained by mshk; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Bun | Firecrawl API key |
| PORT | Server port (default: 5556) |
| FIRECRAWL_API_KEY | Firecrawl API key |
| DB_DIR | Database directory (default: ~/.mcp-rss-crawler) |
{
"mcpServers": {
"rss-crawler": {
"command": "/path/to/bun",
"args": ["run", "/path/to/mcp-rss-crawler/apps/mcp-server/src/mcp-cli.ts"],
"cwd": "/path/to/mcp-rss-crawler",
"env": {
"PORT": "5556",
"DB_DIR": "/path/to/mcp-rss-crawler",
"FIRECRAWL_API_KEY": "fc-<YOUR_FIRECRAWL_API_KEY>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PORT | Configuration value read at startup. | Optional |
| DB_DIR | Filesystem location the server is allowed to use. | Optional |
| FIRECRAWL_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_FIRECRAWL_API_KEY | Credential the server authenticates with. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.