SORACOM MCP Server
A Model Context Protocol (MCP) server for interacting with SORACOM APIs.
README
SORACOM MCP Server
⚠️ EARLY ACCESS: This is an early access project and is provided as-is. There is no guarantee of continued support or maintenance. Use at your own risk.
A Model Context Protocol (MCP) server for interacting with SORACOM APIs.
Quick Start
Prerequisites
- Node.js v22+ (ES modules support)
- SORACOM Auth Key (ID and Token)
Configuration
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
Authentication Methods
There are two ways to authenticate with SORACOM:
- Direct environment variables - Set auth key ID and token directly
- SORACOM CLI profile - Use existing SORACOM CLI profile credentials
Method 1: Using Auth Key Environment Variables
{
"mcpServers": {
"soracom": {
"command": "npx",
"args": ["@soracom-labs/soracom-mcp-server"],
"env": {
"SORACOM_AUTH_KEY_ID": "your-key-id",
"SORACOM_AUTH_KEY": "your-token",
"SORACOM_COVERAGE_TYPE": "jp"
}
}
}
}
Required environment variables:
- SORACOM_AUTH_KEY_ID: Your SORACOM authentication key ID
- SORACOM_AUTH_KEY: Your SORACOM authentication key token
Get your authentication keys from:
- Manage Root User Credentials (Japanese)
- AuthKeys (English)
Method 2: Using SORACOM CLI Profile
If you have configured SORACOM CLI profiles, you can use them instead:
{
"mcpServers": {
"soracom": {
"command": "npx",
"args": ["@soracom-labs/soracom-mcp-server"],
"env": {
"SORACOM_PROFILE": "production"
}
}
}
}
Required environment variable:
- SORACOM_PROFILE: SORACOM CLI profile name
- Credentials are loaded from
~/.soracom/<profile>.json - Profile file should contain
authKeyIdandauthKeyfields - See SORACOM CLI Basic Usage for profile configuration details
- Credentials are loaded from
Common Environment Variable (Both Methods)
- SORACOM_COVERAGE_TYPE: API coverage region
"jp"for Japan coverage"g"for Global coverage- Priority: Environment variable > Profile
coverageType> Default"jp"
That's it! No installation needed - npx will download and run the server automatically.
Security Recommendation
For enhanced security, we recommend creating a SAM (SORACOM Access Management) user with permissions limited to only the necessary API operations, rather than using your root user credentials. Generate the AuthKey ID and Token from this SAM user for use with this MCP server.
Using with Docker
You can also run the MCP server using Docker. Build the image with the following command:
docker build -t soracom-mcp-server:latest .
Settings are like below:
{
"mcpServers": {
"soracom": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"SORACOM_AUTH_KEY_ID",
"-e",
"SORACOM_AUTH_KEY",
"soracom-mcp-server:latest"
],
"env": {
"SORACOM_AUTH_KEY_ID": "your-key-id",
"SORACOM_AUTH_KEY": "your-token",
"SORACOM_COVERAGE_TYPE": "jp"
}
}
}
}
Usage
Command Naming Convention
All commands follow the pattern Category_operationId where:
- Category is the API category (e.g.,
Sim,Billing,Stats) - operationId is the operation name from the SORACOM API
Examples:
Sim_getSim- Get SIM informationBilling_getLatestBilling- Get latest billing informationQuery_searchSims- Search for SIMs
Example Commands in Claude Desktop
Get information for SIM ID "8981100000000000000" using the Sim_getSim command
List all active SIMs with limit 10 using the Sim_listSims command
Show billing for current month using the Billing_getLatestBilling command
Find SIMs with name containing "production" using the Query_searchSims command
Coverage Selection
- Default: Set
SORACOM_COVERAGE_TYPEto"jp"or"g"in config - Per-command: Each command accepts optional
coverageparameter
Available Tools
See Available Tools Documentation for the complete list of supported commands.
Development
See development guides for setup and workflow:
- Local Development Guide - Setup and workflow
- Claude Desktop Development - Testing with Claude Desktop
- Architecture Documentation - Project structure and design
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.