2,500+ MCP servers ready to use
Vinkius

Feedly MCP Server for CrewAI 12 tools — connect in under 2 minutes

Built by Vinkius GDPR 12 Tools Framework

Connect your CrewAI agents to Feedly through Vinkius, pass the Edge URL in the `mcps` parameter and every Feedly tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Feedly Specialist",
    goal="Help users interact with Feedly effectively",
    backstory=(
        "You are an expert at leveraging Feedly tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Feedly "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 12 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Feedly
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

About Feedly MCP Server

Connect your Feedly account to any AI agent and take full control of your news consumption and RSS aggregation through natural conversation.

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

What you can do

  • Collection Orchestration — List all your curated collections and feeds to organize your information flow natively
  • Stream Intelligence — Retrieve the latest articles from specific feeds or entire categories with full metadata flawlessly
  • Read State Management — Mark articles as read or save them for later directly from the cloud without manual UI interaction
  • Content Discovery — Search for new RSS feeds and trending topics across the entire Feedly index flawlessly
  • Board & Tag Organization — List and query articles from your personal boards and tagged content natively
  • User Insights — Access your Feedly profile and subscription metadata through the agent synchronously

The Feedly MCP Server exposes 12 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Feedly to CrewAI via MCP

Follow these steps to integrate the Feedly MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 12 tools from Feedly

Why Use CrewAI with the Feedly MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Feedly through the Model Context Protocol.

01

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

02

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

03

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

04

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

Feedly + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Feedly MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Feedly for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Feedly, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Feedly tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Feedly against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Feedly MCP Tools for CrewAI (12)

These 12 tools become available when you connect Feedly to CrewAI via MCP:

01

get_board_contents

Retrieve articles from a specific board

02

get_entry

Get details for a specific article entry

03

get_profile

Get current Feedly user profile

04

get_stream_contents

Retrieve articles for a specific stream (feed, category, or global)

05

get_subscriptions

List all individual feed subscriptions

06

get_tag_contents

Retrieve articles associated with a specific tag

07

list_boards

List all your Feedly boards (saved for later)

08

list_collections

List all your Feedly collections (categories) and feeds

09

list_tags

List all your Feedly tags

10

mark_as_read

Mark specific articles as read

11

search_feeds

Search for new RSS feeds in the Feedly index

12

search_topics

Search for trending topics or specific interests

Example Prompts for Feedly in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Feedly immediately.

01

"List my Feedly collections."

02

"Show me the latest 5 articles from the 'Tech News' category."

03

"Search for feeds about 'Edge Computing'."

Troubleshooting Feedly MCP Server with CrewAI

Common issues when connecting Feedly to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Feedly + CrewAI FAQ

Common questions about integrating Feedly MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Feedly to CrewAI

Get your token, paste the configuration, and start using 12 tools in under 2 minutes. No API key management needed.