Stanford GDELT MCP Server for CrewAIGive CrewAI instant access to 16 tools to Get Geo Data, Get Themes, Get Timeline Country, and more

Name: Stanford GDELT
Price: 29 USD
Availability: InStock
Rating: 0.2 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Stanford GDELT MCP Server for CrewAI is a standout in the Data Analytics category — giving your AI agent 16 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Stanford GDELT Specialist",
    goal="Help users interact with Stanford GDELT effectively",
    backstory=(
        "You are an expert at leveraging Stanford GDELT 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 Stanford GDELT "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 16 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 Stanford GDELT MCP Server

Connect to the GDELT Project API — the world's largest open platform for monitoring global news media in real time.

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

Article Search — Search global news articles with filters for language, country, date range, and topic
Volume Timelines — Track how media attention to any topic changes over time
Sentiment Analysis — Monitor tone and sentiment shifts in coverage of any subject
Geographic Mapping — Visualize where news events are happening around the world
TV News Search — Search closed caption transcripts from CNN, Fox News, MSNBC, BBC, and more
Theme Analysis — Explore standardized GDELT themes across geopolitics, health, environment, and economics
Language Distribution — See which linguistic communities are covering a topic
Country Distribution — Identify which nations produce the most coverage of specific issues
Proximity Search — Find articles where two terms appear near each other
Word Clouds — Extract dominant terms and concepts from coverage

The Stanford GDELT MCP Server exposes 16 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 16 Stanford GDELT tools available for CrewAI

When CrewAI connects to Stanford GDELT through Vinkius, your AI agent gets direct access to every tool listed below — spanning gdelt, global-news, sentiment-analysis, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get geo data on Stanford GDELT

Each point includes coordinates, location name, and article metadata. Use modes: "PointData" for individual points, "PointHeat" for heatmap data. Get geographic point data for news events

get

Get themes on Stanford GDELT

GDELT uses hundreds of themes from politics, economics, health, environment, technology, and more to classify news content. Get GDELT theme distribution for a topic

get

Get timeline country on Stanford GDELT

Reveals geographic patterns in media attention, identifies when a story goes global, and shows which nations are most interested in specific issues. Get source country distribution timeline

get

Get timeline lang on Stanford GDELT

Reveals which linguistic communities are paying attention to an issue and when interest spreads across language barriers. Get language distribution timeline for a topic

get

Get timeline tone on Stanford GDELT

Positive values indicate positive coverage, negative values indicate negative coverage. Essential for tracking public opinion shifts, crisis communications, and brand reputation monitoring. Get sentiment and tone timeline for a topic

get

Get timeline volume on Stanford GDELT

Essential for tracking media attention, identifying news spikes, and understanding the lifecycle of a story. Default timespan is 3 months. Get news volume timeline for any topic

get

Get tone chart on Stanford GDELT

Shows whether coverage is predominantly positive, negative, or neutral, and the overall emotional intensity of the coverage. Get tone distribution chart for a topic

get

Get tv channels on Stanford GDELT

Use this to understand the scope of TV news coverage available for analysis. Get available TV news channels inventory

get

Get tv timeline on Stanford GDELT

Reveals which stories dominate TV airtime and how TV coverage patterns differ from online news. Get TV news mention volume timeline

get

Get word cloud on Stanford GDELT

Reveals the dominant themes, entities, and concepts associated with a topic in media discourse. Get word cloud data showing key terms for a topic

Search articles on Stanford GDELT

Returns article titles, URLs, dates, source domains, languages, and source countries. Use timespan like "1d" (1 day), "1w" (1 week), "3m" (3 months). Use sourcelang codes like "english", "spanish", "portuguese", "french", "chinese", "arabic". Use sourcecountry codes like "US", "BR", "UK", "FR", "DE". Search global news articles across 100+ languages

Search by country on Stanford GDELT

Country codes follow ISO 2-letter format: US (United States), BR (Brazil), UK (United Kingdom), FR (France), DE (Germany), CN (China), JP (Japan), IN (India), RU (Russia), AU (Australia), CA (Canada), etc. Essential for understanding country-specific media perspectives on global events. Search news articles from a specific country

Search by language on Stanford GDELT

Covers 100+ languages. Language codes include: english, spanish, portuguese, french, german, italian, chinese, japanese, korean, arabic, russian, hindi, turkish, dutch, swedish, polish, and many more. Essential for monitoring how different linguistic communities cover the same event. Search news articles in a specific language

Search by theme on Stanford GDELT

Themes are standardized topic categories like TAX_FNCACT (financial actions), HEALTH_PANDEMIC, ENV_CLIMATECHANGE, TERROR, PROTEST, ELECTION, ECON_BANKRUPTCY, etc. Use this for precise topic-based monitoring. Search articles by GDELT standardized theme

Search nearby on Stanford GDELT

More precise than simple keyword search. Use distance parameter to control proximity (default 10 words). Example: term1="climate", term2="migration", distance=15. Search articles where two terms appear near each other

Search tv on Stanford GDELT

Returns clips with timestamps, station names, transcript snippets, and video preview URLs. Covers CNN, Fox News, MSNBC, BBC, and more. Modes: "ClipGallery" for clips, "StationChart" for station comparison. Search TV news transcripts by keyword

Connect Stanford GDELT to CrewAI via MCP

Follow these steps to wire Stanford GDELT into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

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

Customize the agent

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

Run the crew

Run python crew.py. CrewAI auto-discovers 16 tools from Stanford GDELT

Why Use CrewAI with the Stanford GDELT MCP Server

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

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

Stanford GDELT + CrewAI Use Cases

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

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

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

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

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

Example Prompts for Stanford GDELT in CrewAI

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

"What are the latest news articles about AI regulation?"

"How has sentiment about climate change evolved over the last 3 months?"

"Search for TV news clips mentioning quantum computing"

Troubleshooting Stanford GDELT MCP Server with CrewAI

Common issues when connecting Stanford GDELT to CrewAI through Vinkius, and how to resolve them.

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.

Stanford GDELT + CrewAI FAQ

Common questions about integrating Stanford GDELT MCP Server with CrewAI.

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.