How do I get an API Key for Gigs?

Log in to your Gigs Dashboard, navigate to Settings > API Keys, and you can generate a new Project API Key there.

Can I see real-time data consumption?

Yes! Use the 'get_subscription_usage' tool with a Subscription ID to retrieve the current data, talk, and text consumption for that specific user.

Does Gigs support both eSIM and physical SIM cards?

Yes, Gigs provides unified management for both digital eSIMs and physical hardware. You can list your inventory using the 'list_connectivity_sims' tool.

How do I activate a new subscription?

First, create a user with 'create_telecom_user', then use the 'create_mobile_subscription' tool to attach a specific plan ID to that user.

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

Name: Gigs
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 12 Tools Framework

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

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 Gigs MCP Server

Connect your Gigs telecom-as-a-service account to any AI agent to automate your mobile connectivity workflows through the Model Context Protocol (MCP). Gigs abstracts the complexity of global carriers into a unified API, allowing you to manage mobile plans and SIMs with ease. This MCP server enables you to retrieve connectivity plans, manage subscriber profiles (users), and track real-time data consumption directly through natural conversation.

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

Key Features

Subscription Orchestration — List all active and inactive mobile subscriptions, retrieve detailed configuration metadata, and create new subscriptions instantly.
Real-time Usage Tracking — Retrieve up-to-the-minute consumption data (data, talk, text) for any subscription to monitor user behavior.
User Management — Register new telecom users and manage their profiles programmatically from your chat interface.
Plan Discovery — Access a comprehensive catalog of voice and data plans available in 200+ countries.
SIM Inventory Oversight — List and retrieve metadata for both eSIMs and physical SIM cards.
Project Analytics — Access high-level metadata for your connected Gigs projects to verify settings and connectivity.
Real-time Synchronization — Keep your telecom operations accessible to your AI assistant without leaving your primary workspace.

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

Follow these steps to integrate the Gigs 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 12 tools from Gigs

Why Use CrewAI with the Gigs MCP Server

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

Gigs + CrewAI Use Cases

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

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

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

Gigs MCP Tools for CrewAI (12)

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

create_mobile_subscription

Start new plan

create_telecom_user

Add new user

get_account_details

Get account identity

get_plan_details

Get plan metadata

get_subscription_details

Get subscription metadata

get_subscription_usage

Check data usage

list_connectivity_plans

List mobile plans

list_connectivity_sims

List SIM cards

list_connectivity_users

List telecom users

list_mobile_subscriptions

List all subscriptions

list_telecom_projects

List Gigs projects

verify_api_connection

Check connection

Example Prompts for Gigs in CrewAI

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

"List all available mobile data plans in the catalog."

"How much data has user 'sub_98765' used this month?"

"Create a new subscription for 'john@example.com' using plan 'plan_abc'."

Troubleshooting Gigs MCP Server with CrewAI

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

Gigs + CrewAI FAQ

Common questions about integrating Gigs 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.