Bring Rss Reader
to CrewAI
Learn how to connect Inoreader to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Inoreader MCP Server?
Connect your Inoreader account to any AI agent and transform how you monitor news, blogs, and social feeds through natural language control.
What you can do
- Feed Management — List all your subscriptions and quickly add new RSS/Atom feeds by URL.
- Content Extraction — Fetch article contents from specific feeds, folders, or system streams with advanced filtering.
- Organization — List, create, rename, and delete tags or folders to keep your information architecture clean.
- Engagement — Star important articles, mark items as read, or batch-clear entire streams instantly.
- Unread Monitoring — Get real-time summaries of unread counts across all your categorized content.
How it works
1. Subscribe to this server
2. Enter your Inoreader Access Token (found in your developer preferences)
3. Start querying and organizing your knowledge base from Claude, Cursor, or any MCP client
Who is this for?
- Researchers & Analysts — aggregate intelligence from hundreds of sources and filter for specific keywords using AI.
- Content Creators — monitor industry trends and save inspiration directly to tagged folders without leaving your workspace.
- Information Junkies — keep your 'Unread' counts at zero by letting your AI assistant help you prioritize what truly matters.
Built-in capabilities (10)
Articles will remain but the organizational label is removed. Delete a tag or folder
Use "user/-/state/com.google/starred" to star/unstar an item. Add or remove tags from articles (e.g., Starred)
Get the number of unread items per feed/folder
Get Inoreader user information
Use "user/-/state/com.google/reading-list" for all items. Get articles for a specific feed, folder, or tag
List all user subscriptions (feeds)
List all user tags and folders
Mark all items in a stream as read
Subscribe to a new feed by URL
Rename an existing tag or folder
Why CrewAI?
When paired with CrewAI, Inoreader becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Inoreader 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
mcpsparameter 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
Inoreader in CrewAI
Inoreader and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Inoreader 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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Inoreader in CrewAI
The Inoreader 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 10 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.
* 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
How Vinkius secures
Inoreader for CrewAI
Every tool call from CrewAI to the Inoreader MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I use this to find specific articles across all my subscriptions?
Yes! Use the list_stream_contents tool with the system stream ID user/-/state/com.google/reading-list. You can then ask the AI to filter or search for specific keywords within the returned articles.
Is it possible to star articles directly from the conversation?
Absolutely. Use the edit_tag tool and provide the Article ID with the add parameter set to user/-/state/com.google/starred. This will instantly save the article to your Starred folder in Inoreader.
How do I see how many unread articles I have in each folder?
Run the get_unread_counts tool. It returns a structured list of all your streams (feeds, folders, and tags) along with the precise count of unread items for each.
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.
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.
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.
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.
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.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
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.