2,500+ MCP servers ready to use
Vinkius

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

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to CrowdTangle through Vinkius, pass the Edge URL in the `mcps` parameter and every CrowdTangle 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="CrowdTangle Specialist",
    goal="Help users interact with CrowdTangle effectively",
    backstory=(
        "You are an expert at leveraging CrowdTangle 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 CrowdTangle "
        "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)
CrowdTangle
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 CrowdTangle MCP Server

Integrate CrowdTangle, the public insights tool from Meta, directly into your AI workflow. Monitor social media trends, track how links are being shared across platforms, and identify high-performing content using natural language.

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

  • Post Monitoring — List and search for recent public posts on Facebook, Instagram, and other supported platforms.
  • Viral Discovery — Identify overperforming and viral content based on actual vs. expected interaction.
  • Link Tracking — See which public accounts and pages have shared specific URLs.
  • Leaderboards & Lists — Monitor account leaderboards and manage your custom tracking lists.

The CrowdTangle 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 CrowdTangle to CrewAI via MCP

Follow these steps to integrate the CrowdTangle 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 CrowdTangle

Why Use CrewAI with the CrowdTangle MCP Server

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

CrowdTangle + CrewAI Use Cases

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

01

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

03

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

CrowdTangle MCP Tools for CrewAI (10)

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

01

get_account_details

Touches dashboard settings, API rate limits, and workspace configuration boundaries. Retrieve metadata for your CrowdTangle account

02

get_account_leaderboard

Resolves account rankings, total interactions, and average engagement rates. Get engagement leaderboard for accounts in your lists

03

get_link_shares

Resolves which tracked accounts shared the link, their follower counts, and total interactions generated per share. See which accounts have shared a specific URL

04

get_post_details

Touches reaction breakdowns, share history, and platform-specific metadata boundaries. Get full engagement details for a specific post ID

05

get_top_performing_posts

Resolves "score" metrics (actual vs expected interactions) and associated social media metadata. Get the highest performing posts based on actual vs. expected interaction

06

list_media_posts

Resolves media URLs, content types (Photo, Video), and associated post captions. List recent posts that contain photos or videos

07

list_monitored_lists

Resolves list IDs, names, platform affiliations, and the number of accounts within each list. List all account lists you are tracking

08

list_recent_posts

Resolves post content, platform identifiers (Facebook, Instagram, etc.), account names, and engagement metrics (likes, shares, comments). List recent social media posts tracked by CrowdTangle

09

search_posts_by_keyword

Resolves relevant posts, associated accounts, and comparative performance data. Search for posts across platforms using a keyword

10

search_tracking_lists

Resolves list metadata matching the specified title filter. Search for specific tracking lists by title

Example Prompts for CrowdTangle in CrewAI

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

01

"Search for recent viral posts about 'Electric Vehicles' on Instagram."

02

"Who has shared the link 'https://vinkius.com/blog/mcp-server' recently?"

03

"Show me the engagement leaderboard for my 'Competitors' list."

Troubleshooting CrowdTangle MCP Server with CrewAI

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

CrowdTangle + CrewAI FAQ

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

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