What information do I need to identify an IoT SIM?

Each IoT SIM is uniquely identified by its **ICCID** (Integrated Circuit Card Identifier) -- a 19-20 digit number printed on the SIM card or available in your IoT Control Center dashboard. The ICCID is required for all device-specific operations like activation, suspension, and usage queries. You can list all your devices with `list_devices` to discover ICCIDs for your entire fleet.

How do data pools work and how can I prevent pool exhaustion?

Data pools are shared data plans across multiple IoT SIMs. Instead of each SIM having an individual cap, all devices in the pool draw from a common data bucket. Use `list_data_pools` to see your pools, `get_pool_usage` to check consumption and identify top-consuming devices, and set up alerts before reaching the limit. If a pool is near exhaustion, you can suspend low-priority devices with `suspend_device` or migrate high-usage devices to a different pool with `update_device_settings`.

Can I automatically diagnose why an IoT device went offline?

Yes. Use the `diagnose_connectivity` tool with the device's ICCID. It runs automated checks for network registration status, APN configuration, active data session, signal strength, and known network outages in the device's area. The tool returns detailed diagnostic results with recommended actions -- helping your field engineers resolve connectivity issues without manual portal navigation.

AT&T IoT MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: AT&T IoT
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

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

Connect your AT&T IoT account to any AI agent and take full command of your IoT SIM fleet through natural conversation.

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

Device Inventory -- List all IoT SIMs with ICCIDs, statuses (active, suspended, deactivated), data plan names, and last activity dates
Real-Time Status -- Get live connectivity state, IP address, signal strength, data used/remaining, and suspension reasons for any SIM
Activate & Suspend -- Instantly activate suspended devices or suspend compromised SIMs to block network access and contain costs
Resume Devices -- Restore network access to suspended SIMs after troubleshooting or policy clearance without reprovisioning
Data Usage Tracking -- Retrieve current and historical usage per SIM with daily breakdowns, overage alerts, and cycle forecasts
Data Pool Management -- List shared data pools, monitor aggregate consumption, identify top-consuming devices, and prevent pool exhaustion
Device Configuration -- Update rate limits, APN settings, and pool assignments to optimize performance or migrate devices between plans
Automated Diagnostics -- Run connectivity troubleshooting checks including network registration, APN config, data session status, and known outages

The AT&T IoT 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 AT&T IoT to CrewAI via MCP

Follow these steps to integrate the AT&T IoT 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 10 tools from AT&T IoT

Why Use CrewAI with the AT&T IoT MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with AT&T IoT 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 IoT + CrewAI Use Cases

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

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

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

AT&T IoT MCP Tools for CrewAI (10)

These 10 tools become available when you connect AT&T IoT to CrewAI via MCP:

activate_device

Returns activation timestamp and assigned IP. Use to onboard new devices or restore service after maintenance. Activate a suspended or deactivated IoT SIM

diagnose_connectivity

Returns diagnostic results and recommended actions. Use for rapid troubleshooting of offline devices. Run automated diagnostics to troubleshoot IoT device connectivity

get_data_usage

Use to monitor plan limits, identify heavy users, or forecast billing. Retrieve current and historical data usage for an IoT SIM

get_device_status

Use to troubleshoot offline devices or verify data allowance. Get real-time connectivity and data status of an IoT SIM

get_pool_usage

Use to prevent pool exhaustion or reallocate unused data. Get detailed usage metrics for a specific data pool

list_data_pools

Use to manage enterprise data sharing across fleets. List shared data pools configured for IoT devices

list_devices

Use to audit fleet inventory, identify inactive SIMs, or verify provisioning status. List all IoT SIMs/devices managed in AT&T Control Center

resume_device

Use to restore service after troubleshooting or policy clearance. Resume network access for a suspended IoT SIM

suspend_device

Use for lost/stolen devices, cost containment, or decommissioning. Suspend an IoT SIM to block network access

update_device_settings

Requires ICCID and JSON settings object. Use to optimize performance or migrate devices between plans. Update configuration settings for an IoT device

Example Prompts for AT&T IoT in CrewAI

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

"List all my IoT devices and show me which ones are suspended."

"Device ICCID 8901234567890123456 is offline. Run diagnostics and tell me what's wrong."

"Check the data pool usage for 'Enterprise-Fleet-A' and tell me our top 5 consuming devices."

Troubleshooting AT&T IoT MCP Server with CrewAI

Common issues when connecting AT&T IoT 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 IoT + CrewAI FAQ

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