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 LangChain 10 tools — connect in under 2 minutes

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

python.langchain.com/docs/integrations/tools/mcp

Built by Vinkius GDPR 10 Tools Framework

LangChain is the leading Python framework for composable LLM applications. Connect AT&T IoT through Vinkius and LangChain agents can call every tool natively. combine them with retrievers, memory, and output parsers for sophisticated AI pipelines.

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

import asyncio
from langchain_mcp_adapters.client import MultiServerMCPClient
from langchain_openai import ChatOpenAI
from langgraph.prebuilt import create_react_agent

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    async with MultiServerMCPClient({
        "att-iot": {
            "transport": "streamable_http",
            "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
        }
    }) as client:
        tools = client.get_tools()
        agent = create_react_agent(
            ChatOpenAI(model="gpt-4o"),
            tools,
        )
        response = await agent.ainvoke({
            "messages": [{
                "role": "user",
                "content": "Using AT&T IoT, show me what tools are available.",
            }]
        })
        print(response["messages"][-1].content)

asyncio.run(main())

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.

LangChain's ecosystem of 500+ components combines seamlessly with AT&T IoT through native MCP adapters. Connect 10 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.

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 LangChain 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 LangChain via MCP

Follow these steps to integrate the AT&T IoT MCP Server with LangChain.

Install dependencies

Run pip install langchain langchain-mcp-adapters langgraph langchain-openai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

Run the agent

Save the code and run python agent.py

Explore tools

The agent discovers 10 tools from AT&T IoT via MCP

Why Use LangChain with the AT&T IoT MCP Server

LangChain provides unique advantages when paired with AT&T IoT through the Model Context Protocol.

The largest ecosystem of integrations, chains, and agents. combine AT&T IoT MCP tools with 500+ LangChain components

Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step

LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging

Memory and conversation persistence let agents maintain context across AT&T IoT queries for multi-turn workflows

AT&T IoT + LangChain Use Cases

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

RAG with live data: combine AT&T IoT tool results with vector store retrievals for answers grounded in both real-time and historical data

Autonomous research agents: LangChain agents query AT&T IoT, synthesize findings, and generate comprehensive research reports

Multi-tool orchestration: chain AT&T IoT tools with web scrapers, databases, and calculators in a single agent run

Production monitoring: use LangSmith to trace every AT&T IoT tool call, measure latency, and optimize your agent's performance

AT&T IoT MCP Tools for LangChain (10)

These 10 tools become available when you connect AT&T IoT to LangChain 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 LangChain

Ready-to-use prompts you can give your LangChain 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 LangChain

Common issues when connecting AT&T IoT to LangChain through the Vinkius, and how to resolve them.

MultiServerMCPClient not found

Install: pip install langchain-mcp-adapters

AT&T IoT + LangChain FAQ

Common questions about integrating AT&T IoT MCP Server with LangChain.

How does LangChain connect to MCP servers?

Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.

Which LangChain agent types work with MCP?

All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.