How do I find my X Ads Access Token?

You must create a developer account at [**developer.x.com**](https://developer.x.com/), create a Project/App, and perform the OAuth flow to generate a Bearer Token. Copy and paste it below.

Can the agent list my promoted tweets?

Yes. Use the `list_promoted_tweets` tool providing your Ad Account ID. Your agent will retrieve metadata for all tweets currently being used in your advertising campaigns.

Is it possible to see analytics for specific line items?

Yes. The `get_analytics` tool allows your agent to fetch daily performance metrics for specific entity IDs (campaigns, line items, or ads) by providing a date range.

X Ads (Twitter) MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: X Ads (Twitter)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="X Ads (Twitter) Specialist",
    goal="Help users interact with X Ads (Twitter) effectively",
    backstory=(
        "You are an expert at leveraging X Ads (Twitter) 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 X Ads (Twitter) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 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 X Ads (Twitter) MCP Server

Empower your AI agent to orchestrate your entire advertising ecosystem on X (formerly Twitter) with X Ads, the platform for engaging with the global conversation in real-time. By connecting X Ads to your agent, you transform complex campaign management into a natural conversation. Your agent can instantly list your ad accounts, audit line item performance, and retrieve detailed analytics without you ever touching a dashboard. Whether you are driving website traffic or scaled video views, your agent acts as a real-time ad analyst, ensuring your marketing is always optimized and trend-aware.

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

What you can do

Account Auditing — List all ad accounts in your profile and retrieve detailed metadata, including status and funding instruments.
Campaign Oversight — List and audit campaigns, line items, and individual ads to maintain a structured view of your efforts.
Performance Intelligence — Retrieve detailed advertising analytics with flexible dates and metric groups to understand ROI.
Creative Governance — List promoted tweets and creative assets to ensure your content is correctly published and active.
Operational Monitoring — Quickly retrieve account-wide information to maintain strict organizational control.

The X Ads (Twitter) MCP Server exposes 8 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 X Ads (Twitter) to CrewAI via MCP

Follow these steps to integrate the X Ads (Twitter) MCP Server with CrewAI.

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 8 tools from X Ads (Twitter)

Why Use CrewAI with the X Ads (Twitter) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with X Ads (Twitter) 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 the 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

X Ads (Twitter) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the X Ads (Twitter) MCP Server delivers measurable value.

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

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

X Ads (Twitter) MCP Tools for CrewAI (8)

These 8 tools become available when you connect X Ads (Twitter) to CrewAI via MCP:

get_ad_account

Get details for a specific ad account

get_analytics

Get analytics for ad entities

list_ad_accounts

List X (Twitter) Ads accounts

list_ads

List ads for an ad account

list_campaigns

List campaigns for an ad account

list_funding_instruments

List funding instruments for an account

list_line_items

List line items for an ad account

list_promoted_tweets

List promoted tweets for an account

Example Prompts for X Ads (Twitter) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with X Ads (Twitter) immediately.

"List all my X ad accounts."

"Show me active campaigns for account ID xxxx."

"Get an engagement report for last week."

Troubleshooting X Ads (Twitter) MCP Server with CrewAI

Common issues when connecting X Ads (Twitter) to CrewAI through the 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

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

X Ads (Twitter) + CrewAI FAQ

Common questions about integrating X Ads (Twitter) 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.