4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Miniflux (RSS Reader) MCP Server

Bring Rss Reader
to CrewAI

Learn how to connect Miniflux (RSS Reader) to CrewAI and start using 46 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Create Api KeyCreate CategoryCreate FeedCreate UserDelete Api KeyDelete CategoryDelete FeedDelete UserDiscover SubscriptionsExport OpmlFetch Entry ContentFlush HistoryGet EntryGet FeedGet Feed CountersGet Feed IconGet IconGet Integrations StatusGet MeGet UserGet VersionHealthcheckImport EntryImport OpmlList Api KeysList CategoriesList Category EntriesList EntriesList Feed EntriesList FeedsList UsersLivenessMark Category As ReadMark Feed As ReadMark User As ReadReadinessRefresh All FeedsRefresh CategoryRefresh FeedSave EntryToggle Entry BookmarkUpdate CategoryUpdate Entries StatusUpdate EntryUpdate FeedUpdate User

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Miniflux (RSS Reader)

What is the Miniflux (RSS Reader) MCP Server?

Connect your Miniflux instance to any AI agent and transform how you consume information. Manage your RSS feeds, read articles, and organize your knowledge base through natural conversation.

What you can do

  • Feed Discovery & Management — Discover RSS feeds from any URL and manage your subscriptions effortlessly with tools like discover_subscriptions and create_feed.
  • Article Reading — List entries, fetch full content, and mark items as read or unread using list_entries and fetch_entry_content.
  • Organization — Categorize feeds and use bookmarks to save important information with list_categories and toggle_entry_bookmark.
  • System Control — Export/Import OPML files and manage your user profile and API keys directly.

How it works

  1. Subscribe to this server
  2. Enter your Miniflux Instance URL and API Key
  3. Start reading and managing your news from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Researchers — aggregate sources and query specific topics across all subscriptions without leaving your research environment.
  • Developers — stay updated with technical blogs and releases directly from your IDE.
  • Content Curators — quickly filter, search, and bookmark relevant articles for newsletters or social media.

Built-in capabilities (46)

create_api_key

Create a new API key

create_category

Create a category

create_feed

Create a new feed

create_user

Create a user (Admin only)

delete_api_key

Delete an API key

delete_category

Delete a category

delete_feed

Remove a feed

delete_user

Delete a user (Admin only)

discover_subscriptions

Discover subscriptions from a URL

export_opml

OPML Export

fetch_entry_content

Fetch original article content

flush_history

Flush history

get_entry

Get a single entry

get_feed

Get a specific feed

get_feed_counters

Fetch unread and read counters

get_feed_icon

Get feed icon by feed ID

get_icon

Get feed icon by icon ID

get_integrations_status

Check if any third-party integrations are enabled

get_me

Get current user information

get_user

Get a specific user (Admin only)

get_version

Get application version and build info

healthcheck

Healthcheck (checks DB)

import_entry

Import an entry manually

import_opml

OPML Import

list_api_keys

List API keys

list_categories

Get all categories

list_category_entries

Get entries for a specific category

list_entries

Get entries with filters

list_feed_entries

Get entries for a specific feed

list_feeds

Get all feeds

list_users

Get all users (Admin only)

liveness

Liveness probe

mark_category_as_read

Mark all entries in a category as read

mark_feed_as_read

Mark all entries of a feed as read

mark_user_as_read

Mark all entries for a user as read

readiness

Readiness probe

refresh_all_feeds

Refresh all feeds (background)

refresh_category

Refresh all feeds in a category

refresh_feed

Refresh a specific feed (synchronous)

save_entry

Save entry to third-party services

toggle_entry_bookmark

Toggle entry bookmark (starred)

update_category

Update a category

update_entries_status

Update status of multiple entries (e.g., mark as read)

update_entry

Update entry title or content

update_feed

Update a feed

update_user

Update a user (Admin only)

Why CrewAI?

When paired with CrewAI, Miniflux (RSS Reader) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Miniflux (RSS Reader) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

Miniflux (RSS Reader) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Miniflux (RSS Reader) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Miniflux (RSS Reader) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Miniflux (RSS Reader) in CrewAI

The Miniflux (RSS Reader) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 46 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Miniflux (RSS Reader)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Miniflux (RSS Reader) for CrewAI

Every tool call from CrewAI to the Miniflux (RSS Reader) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I find RSS feeds from a website URL automatically?

Yes! Use the discover_subscriptions tool with any website URL. The agent will scan the site and return all available RSS/Atom feed links found.

02

How do I mark all articles in a specific feed as read?

Simply use the mark_feed_as_read action providing the feed_id. This will instantly update the status of all entries within that feed to 'read'.

03

Can I search for specific keywords across all my articles?

Yes. Use the list_entries tool and provide a keyword in the search parameter. You can also filter by status (read/unread) or starred items.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →