What are Open Gateway / CAMARA APIs and why do they matter?

Open Gateway is a global initiative by GSMA and the Linux Foundation that standardizes telecom network APIs across carriers. CAMARA is the open-source project defining these API specifications. Instead of carrier-specific integrations, developers get universal, consistent endpoints for Number Verify, Device Location, SIM Swap, Quality on Demand, and more. AT&T is a founding participant, meaning these APIs work the same way across compatible networks worldwide.

Does Device Location require user consent?

Yes. Per CAMARA standards, the Device Location API requires explicit user consent before returning any positioning data. The API will fail with an authentication error if consent has not been granted. This is a security and privacy safeguard -- network-level location cannot be retrieved silently without the user's knowledge.

What is Network Slicing and when should I use it?

Network Slicing creates logically isolated 5G network segments with guaranteed SLA parameters (latency, bandwidth, reliability). Use it for IoT deployments requiring guaranteed connectivity, private enterprise networks, mission-critical applications like remote surgery or autonomous vehicles, and any scenario where best-effort public network performance is insufficient. You can create, monitor, and delete slices directly through your AI agent.

AT&T 5G MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: AT&T 5G
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

Connect your CrewAI agents to AT&T 5G through Vinkius, pass the Edge URL in the `mcps` parameter and every AT&T 5G 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="AT&T 5G Specialist",
    goal="Help users interact with AT&T 5G effectively",
    backstory=(
        "You are an expert at leveraging AT&T 5G 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 AT&T 5G "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 9 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 AT&T 5G MCP Server

Connect your AT&T 5G account to any AI agent and unlock the full power of Open Gateway / CAMARA-compliant network APIs through natural conversation.

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

Number Verify -- Silently confirm a user's phone number matches their current device without SMS OTP friction
Device Location -- Get approximate geographic positioning via network-based cell tower triangulation (with user consent)
SIM Swap Detection -- Detect recent SIM card changes to prevent account takeovers and fraud before they happen
Quality on Demand -- Request guaranteed network profiles (low latency, high throughput, reliable transmission) for critical sessions
Network Slicing -- Provision, monitor, and decommission dedicated 5G network slices with custom SLA parameters for enterprise use
Roaming Status -- Check if a device is roaming on a foreign network and apply correct billing or routing rules
Session Auditing -- List active and historical QoD sessions to audit premium service consumption

The AT&T 5G MCP Server exposes 9 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 AT&T 5G to CrewAI via MCP

Follow these steps to integrate the AT&T 5G 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 9 tools from AT&T 5G

Why Use CrewAI with the AT&T 5G MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AT&T 5G 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

AT&T 5G + CrewAI Use Cases

Practical scenarios where CrewAI combined with the AT&T 5G MCP Server delivers measurable value.

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

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

AT&T 5G MCP Tools for CrewAI (9)

These 9 tools become available when you connect AT&T 5G to CrewAI via MCP:

check_roaming_status

Use this to apply correct billing rates, trigger roaming alerts, or optimize routing for international travelers. Check if a device is currently roaming on a foreign network

check_sim_swap

Returns days since last swap or a boolean indicating recent activity. Use this to block account takeovers attempts, verify identity before password resets, or trigger step-up authentication. Detect if a SIM card has been swapped recently for fraud prevention

create_network_slice

Requires slice name, SLA profile, and target device group. Returns slice ID and provisioning status. Use this for IoT deployments, private enterprise networks, or guaranteed performance applications. Provision a new dedicated 5G network slice for an enterprise use case

delete_network_slice

Requires slice ID. Use this to clean up unused slices, reduce costs, or retire temporary deployments. Decommission and delete an existing 5G network slice

get_device_location

Requires user consent per CAMARA standards. Returns latitude, longitude, and accuracy radius in meters. Use this for geo-fencing, localized content delivery, or emergency services routing. Do not use for precise GPS tracking. Get approximate geographic location of an AT&T 5G device

get_network_slice_info

Includes SLA parameters, allocated resources, and connected devices. Use this to monitor slice health or verify enterprise SLA compliance. Get details of a specific 5G network slice

list_network_sessions

Use this to audit network usage, track premium service consumption, or troubleshoot active sessions. List active and historical network QoD sessions

request_quality_on_demand

Choose profiles like "low_latency" (gaming/VR), "high_throughput" (video), or "reliable_transmission" (IoT). Returns session ID and active duration. Use this to optimize real-time applications, prioritize critical downloads, or enhance remote worker connectivity. Request guaranteed network quality (low latency/high bandwidth) for a session

verify_number

Eliminates SMS OTP friction. Requires the phone number in E.164 format (e.g., +12125551234). Returns verification status and confidence score. Use this for seamless user onboarding, secure login, or fraud prevention. Silently verify a user's phone number without SMS OTP

Example Prompts for AT&T 5G in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with AT&T 5G immediately.

"Check if the phone number +12125551234 had a SIM swap in the last 7 days."

"Create a low-latency network slice called 'TradingFloor-Prime' for our enterprise deployment."

"Verify the phone number +14155559876 for user login without sending an SMS code."

Troubleshooting AT&T 5G MCP Server with CrewAI

Common issues when connecting AT&T 5G 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

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

AT&T 5G + CrewAI FAQ

Common questions about integrating AT&T 5G 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.