SIMSY - Your mobile network. Open. Secure. Programmable.

Connected Britain 2025

Come and meet us in the Start Up Village.

The SIMSY team are excited to be attending Connected Britain 2025 at the Excel London on 24th and 25th September 2025. Come and visit us in the Start Up Village where we will be demonstrating our advanced connectivity solution and how customers can utilise our recently released MCP server.

For customers wanting to find out more about our Mobile App and the brand new Hotspot Bridge App, you will find the links below which will guide you to download the apps and get you started.

SIMSY AppHotspot Bridge
Visitors to our stand can get a free eSIM and 1GB of data (Zones 1 & 2).
Just ask one of the Team!

SIMSY MCP Server

Welcome to the SIMSY MCP Server! This guide will help you connect to the server from a variety of clients, including those that support SSE, streamable HTTP, and those that require a local proxy using mcp-remote.

🚀 Endpoints

SSE:
https://mcp.s-imsy.com/sse
HTTP (streamable):
https://mcp.s-imsy.com/mcp

🔑 Authentication

You must obtain your MCP Token from the SIMSY App.

The server expects your MCP Token as a Bearer token in the Authorization header:

Authorization: Bearer YOUR_TOKEN_HERE

🛠️ Tools Available

General Group

1. getSims

  • Purpose: Get an overview of all SIMs on your account.
  • Returns: SIM ID, SIM Name, Network Status, Total number of SIMs
  • Usage: Use this tool to list and identify the SIMs you want to work with.

2. getSimInfo

  • Purpose: Get detailed information about a specific SIM.
  • Input: SIM Name (as shown in the getSims output)
  • Returns: latestActivity, endpointStatus.active (true/false), endpointNetworkStatus.active (true/false), latestRatType.name, latestServingOperatorDescription, latestCountryName, usageRolling24H (in MB), usageRolling7D (in MB), usageRolling28D (in MB)
  • Usage: Use this tool to get a detailed, normalized view of a SIM's status and usage.

3. sendSms

  • Purpose: Send an SMS message to a SIM card.
  • Input: SIM Name, Message Text, Token
  • Returns: API response from the SMS send operation
  • Usage: Use this tool to send SMS messages to your SIMs.

4. restartSim

  • Purpose: Force a SIM to detach from the network and reconnect (useful for troubleshooting data session issues).
  • Input: SIM Name, Token
  • Returns: API response from the reset operation
  • Usage: Use this tool if a SIM is connected but not getting a data session.

5. accountEvents

  • Purpose: Retrieve account events with optional date and pagination filters.
  • Input: Token (required), from (optional), to (optional), offset (optional), limit (default 200), sortOrder (optional), filter (optional)
  • Returns: List of account events
  • Usage: Use this tool to audit or review activity on your account.

Device Management Group

1. storeDeviceKeyValue

  • Purpose: Store or update a key-value for a device (router/ethernet) on the SIMSY network.
  • Input: Token, Endpoint ID, Key (e.g. ROUTER_MFR, ROUTER_MOD, ROUTER_USER, ROUTER_PW, ETH1_NAME, ETH1_IP, ETH1_PORT, etc.), Value (string or integer)
  • Returns: Confirmation of storage
  • Usage: Use this tool to save device details (router make/model, admin, password, ethernet port info) for later automation.

2. getDeviceKeyValues

  • Purpose: Retrieve all key-values for a device (router/ethernet) on the SIMSY network.
  • Input: Token, Endpoint ID
  • Returns: All stored key-values for the device
  • Usage: Use this tool to fetch all saved device details for configuration or troubleshooting.

3. deleteDeviceKeyValue

  • Purpose: Delete a specific key-value for a device (router/ethernet) on the SIMSY network.
  • Input: Token, Endpoint ID, Key
  • Returns: Confirmation of deletion
  • Usage: Use this tool to remove outdated or incorrect device details.

1. Connecting with Direct HTTP/SSE (for clients that support it)

Example JSON Config

{
  "mcpServers": {
    "simsy-remote": {
      "type": "http",
      "url": "https://mcp.s-imsy.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace YOUR_TOKEN_HERE with your actual MCP Token from the SIMSY App.

Works With:
  • Some advanced MCP clients (future versions of Claude, Cursor, Windsurf, etc.)
  • Any tool that allows custom HTTP headers in its MCP config

2. Connecting with mcp-remote (for stdio-only clients like VS Code, Claude Desktop, Cursor, Windsurf)

Install Requirements

  • Node.js (v18+)
  • npx (comes with Node.js)

Example JSON Config

{
  "mcpServers": {
    "simsy-remote": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.s-imsy.com/sse",
        "--header",
        "Authorization:Bearer ${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "YOUR_TOKEN_HERE"
      }
    }
  }
}
  • Note: No space after the colon in "Authorization:Bearer ..." to avoid argument parsing bugs in some clients.
  • Replace YOUR_TOKEN_HERE with your MCP Token from the SIMSY App.
Works With:
  • VS Code (via Roo Code/Anthropic MCP extension)
  • Claude Desktop
  • Cursor
  • Windsurf
  • Any other stdio-only MCP client
How it works:
  • mcp-remote runs locally, connects to your remote MCP server, and handles authentication.
  • Your client connects to mcp-remote as if it were a local MCP server.

3. Troubleshooting

  • Authentication Fails: Double-check your MCP Token from the SIMSY App. Make sure it is current and entered exactly.
  • Client Does Not Support HTTP/SSE: Use the mcp-remote method as described above.
  • Still Having Issues?
    • Make sure your Node.js and npx are up to date.
    • Check the mcp-remote documentation for advanced flags and troubleshooting.

4. Security Note

  • Never share your MCP Token. Treat it like a password.
  • If you believe your token is compromised, generate a new one in the SIMSY App.

5. References

Back to Documentation