2,500+ MCP servers ready to use
Vinkius

The Guardian MCP Server for CrewAI 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to The Guardian through Vinkius, pass the Edge URL in the `mcps` parameter and every The Guardian 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="The Guardian Specialist",
    goal="Help users interact with The Guardian effectively",
    backstory=(
        "You are an expert at leveraging The Guardian 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 The Guardian "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

Connect to The Guardian Open Platform and unlock programmatic access to one of the world's most respected newsrooms through natural conversation.

When paired with CrewAI, The Guardian becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call The Guardian 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

  • Content Search — Run full-text queries across the entire Guardian archive with filters by section, tag, date range, and custom ordering
  • Article Retrieval — Fetch the complete body text, byline, publication date, and editorial metadata for any individual article
  • Section Browsing — List all editorial sections (e.g. Technology, Politics, Sport) and browse their latest or most-viewed content
  • Tag Discovery — Explore the taxonomy of keywords, contributors, series, and tones used to categorize Guardian journalism
  • Regional Editions — Query content across UK, US, Australia, and International editions
  • Date-Range Research — Retrieve articles published within specific time windows for historical analysis or event tracking

The The Guardian MCP Server exposes 10 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 The Guardian to CrewAI via MCP

Follow these steps to integrate the The Guardian 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 10 tools from The Guardian

Why Use CrewAI with the The Guardian MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with The Guardian 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

The Guardian + CrewAI Use Cases

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

01

Automated multi-step research: a reconnaissance agent queries The Guardian 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 The Guardian, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain The Guardian 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 The Guardian against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

The Guardian MCP Tools for CrewAI (10)

These 10 tools become available when you connect The Guardian to CrewAI via MCP:

01

get_item

g. "world/2026/apr/08/example-article"). Get the full content of a specific Guardian article or item

02

get_latest_content

Ordered by most recent first. Get the most recent articles from The Guardian

03

get_section_details

Get editorial highlights and most-viewed content for a section

04

list_editions

List available Guardian regional editions

05

list_sections

g. technology, politics, sport). Optionally filter by name. List all editorial sections available on The Guardian

06

list_tags

Filter by query, section, or tag type (keyword, series, contributor, tone, type, blog). List tags used to categorize Guardian content

07

search_by_date_range

Useful for historical research or tracking recent events. Search Guardian content within a specific date range

08

search_by_section

g. "technology", "world", "sport"). Supports pagination and ordering. Browse content within a specific Guardian section

09

search_by_tag

g. "technology/artificial-intelligence", "tone/features"). Supports pagination. Browse content tagged with a specific Guardian tag

10

search_content

Supports filtering by section, tag, date range, ordering, and pagination. Search articles and content on The Guardian

Example Prompts for The Guardian in CrewAI

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

01

"Search The Guardian for recent articles about artificial intelligence in the technology section."

02

"What are the main editorial sections available on The Guardian?"

03

"Find all Guardian articles about climate change published between January and March 2026."

Troubleshooting The Guardian MCP Server with CrewAI

Common issues when connecting The Guardian 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.

The Guardian + CrewAI FAQ

Common questions about integrating The Guardian 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 The Guardian to CrewAI

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