1NCE API MCP Server

@1NCE-GmbH

About 1NCE API MCP Server

MCP Server for integration of LLMs with the 1NCE Management API

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "1nce-mcp-server": {
      "command": "python",
      "args": [
        "1nce_mcp.py"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is 1NCE API MCP Server?

This MCP server enables AI agents to interact with the 1NCE IoT connectivity management platform through natural language. It provides a middleware layer that connects Large Language Models to the 1NCE API for managing IoT connectivity, allowing AI assistants to manage connected devices.

How to use 1NCE API MCP Server?

Install dependencies with pip install fastmcp httpx, set the environment variables ONCE_CLIENT_ID and ONCE_CLIENT_SECRET with your 1NCE API credentials, then install via the FastMCP CLI (fastmcp install 1nce_mcp.py) or run directly (python 1nce_mcp.py). The server can be used programmatically with a FastMCP client.

Key features of 1NCE API MCP Server

OAuth 2.0 token-based authentication with the 1NCE API
Query available IoT connectivity products
Create and track orders
Monitor and configure SIM cards
Direct resource access to SIM status and product data
Pre-defined interaction templates for common tasks

Use cases of 1NCE API MCP Server

Check SIM status and remaining data quota for a connected device
Create a new order for SIM cards with a customer reference
Monitor SIM usage statistics and event history over a time period
Update SIM configuration, including status, label, and IMEI lock
Trigger a connectivity reset for a SIM card

FAQ from 1NCE API MCP Server

What does 1NCE API MCP Server do?

It is a middleware layer that connects Large Language Models to the 1NCE IoT connectivity management API, enabling natural language interactions for managing SIM cards, orders, and products.

What are the prerequisites to use this server?

Python 3.8+, FastMCP v2, and a 1NCE account with API credentials are required.

How is authentication handled?

OAuth 2.0 token-based authentication is used. Credentials are set as environment variables (ONCE_CLIENT_ID and ONCE_CLIENT_SECRET). Access tokens are obtained dynamically and not stored persistently.

What tools does the server expose?

Product management (get_all_products), order management (get_all_orders, get_order_by_number, create_order), and SIM management tools for status, quotas, usage, events, configuration, and connectivity reset.

What are the security considerations?

The server prioritizes read operations over write operations. Authentication uses OAuth 2.0 with Basic Authentication, and access tokens are not stored persistently.

Frequently asked questions