2,500+ MCP servers ready to use
Vinkius

AT&T IoT MCP Server for Claude Desktop 10 tools โ€” connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

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.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setupยทjson
{
  "mcpServers": {
    "att-iot": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
AT&T IoT
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.

Claude Desktop is the definitive way to connect AT&T IoT to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

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 Claude Desktop 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 Claude Desktop via MCP

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

01

Open Claude Desktop Settings

Go to Settings โ†’ Developer โ†’ Edit Config to open claude_desktop_config.json

02

Add the MCP Server

Paste the configuration above into the mcpServers section

03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

04

Start using AT&T IoT

Look for the ๐Ÿ”Œ icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the AT&T IoT MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with AT&T IoT through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

AT&T IoT + Claude Desktop Use Cases

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

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

AT&T IoT MCP Tools for Claude Desktop (10)

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

01

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

02

diagnose_connectivity

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

03

get_data_usage

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

04

get_device_status

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

05

get_pool_usage

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

06

list_data_pools

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

07

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

08

resume_device

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

09

suspend_device

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

10

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 Claude Desktop

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

01

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

02

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

03

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

Troubleshooting AT&T IoT MCP Server with Claude Desktop

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

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the ๐Ÿ”Œ icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

AT&T IoT + Claude Desktop FAQ

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

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the ๐Ÿ”Œ icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Connect AT&T IoT to Claude Desktop

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.