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

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

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install AT&T IoT and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "att-iot": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

GitHub Copilot Agent mode brings AT&T IoT data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the AT&T IoT MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using AT&T IoT

Ask Copilot: "Using AT&T IoT, help me...". 10 tools available

Why Use VS Code Copilot with the AT&T IoT MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with AT&T IoT through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

AT&T IoT + VS Code Copilot Use Cases

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

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

AT&T IoT MCP Tools for VS Code Copilot (10)

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

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

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

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

AT&T IoT + VS Code Copilot FAQ

Common questions about integrating AT&T IoT MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.