Skip to main content
Glama

meisimusa-mcp

The MCP (Model Context Protocol) server for MeiSIM USA. Two things in one server:

  1. Real US phone numbers for your AI agent (API key). List the numbers on your account, read the texts they receive, wait for the next one, send texts, check the wallet and buy more numbers. The numbers are real carrier lines, not virtual numbers.

  2. Travel eSIMs and retail US plans (no key). Search plans for about 200 countries, get a quote, pay by card on a Stripe page, get the install QR, top up a line.

"Which of my numbers got a text in the last hour?" → read_messages "Wait for the clinic's reply on 423 432 2309 and read it back" → wait_for_message "Text +1 212 555 0100 from my number: running ten minutes late" → send_message "I'm going to Italy for 10 days, get me 5GB" → search_plans, purchase, get_activation

Connect

Remote, nothing to install. Add https://mcp.meisimusa.com/mcp as a custom connector or HTTP MCP server. For the tools on your own numbers, send your API key on the connection:

# Claude Code
claude mcp add --transport http meisim https://mcp.meisimusa.com/mcp --header "Authorization: Bearer YOUR_KEY"
// Cursor, Windsurf and other clients with an mcp.json
{
  "mcpServers": {
    "meisim": {
      "type": "http",
      "url": "https://mcp.meisimusa.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

Without a key the retail tools still work and the number tools answer with where to apply.

Local (stdio), for Claude Desktop, Cursor, Zed:

// claude_desktop_config.json
{
  "mcpServers": {
    "meisimusa": {
      "command": "npx",
      "args": ["-y", "meisimusa-mcp"],
      "env": { "MEISIMUSA_API_KEY": "YOUR_KEY" }
    }
  }
}

Get an API key. Sign up at https://www.meisimusa.com/get-started.html. Every account passes an ID check or a review by a person before it gets a key: one that clears the automatic checks opens in minutes, any other is reviewed by a person, usually the same day. Keys are the account: they say which numbers are yours, whose prepaid wallet pays, and what the account may do (sending, voice, a daily spending limit).

Related MCP server: AgentPhone MCP Server

Tools

Your numbers (API key)

Tool

What it does

Wraps

get_account

Company, status, wallet balance, how many numbers you may still activate today

GET /api/v1/me, GET /dealer/wallet

get_number_pricing

What a new number costs on your account, daily or monthly, with or without voice

GET /dealer/sms-lines/offer

buy_numbers

Order numbers from the prepaid wallet; prepaid, no returns; customer_reference makes a retry safe

POST /api/v1/sms/order

get_order

Status of an order, the numbers delivered so far, what was charged

GET /api/v1/sms/orders/:id

list_my_numbers

Your numbers, paged, with billing and the date each is paid through

GET /api/v1/sms/lines

read_messages

Texts received, newest first; filter by number and since

GET /api/v1/sms/messages

wait_for_message

Block up to 50 s for the next text on a number, then return it

polls the same

send_message

A text from one of your numbers (sending is enabled per account)

POST /api/v1/sms/lines/:number/send

Money rules the server enforces by design: buy_numbers always sends a customer_reference (yours or a generated one) and the backend treats it as an idempotency key, so an AI retry cannot order twice. The account's daily spending limit and wallet balance are enforced server-side and come back as structured errors (payment_required, rate_limited), never retried silently. The agent cannot add money to the wallet.

Voice: a number bought with voice: true also takes and makes calls over SIP. The SIP login is shown on your MeiSIM dashboard, not through this server.

Retail (no key)

Tool

What it does

Wraps

get_ai_line_offer

The live offer for US phone lines for AI agents: monthly prices, the lower price per line for more lines, first-term minimum, what a line includes, how to sign up

GET /web/ai-lines/offer

search_plans

Travel eSIM plans for a country, USD

GET /mm/products?country=

get_quote

Price breakdown for one plan

GET /mm/products/:id

search_us_numbers

Retail US phone plans (a line on a phone, paid by card)

GET /mm/products?country=US

purchase

A Stripe payment link; the eSIM is emailed when paid

POST /web/checkout

get_activation

Order status and the install QR

GET /web/order/:id

topup_lookup, topup_start

Refill an existing US line

/web/topup/*

The customer pays their own card on Stripe's hosted page; the server never sees card data. Every purchase carries an idempotency key.

Claude Connectors Directory build (/mcp-directory)

https://mcp.meisimusa.com/mcp-directory is the listing in the Claude Connectors Directory. It needs no login and exposes only public, read-only data, AI phone lines first:

Tool

What it does

Wraps

get_ai_line_offer

The live offer for US phone lines for AI agents: monthly prices (texts, and with voice over SIP), first-term minimum, what a line includes, delivery, payment methods, the lower price per line for more lines and who to write to from 1,000 lines, apply + docs links

GET /web/ai-lines/offer (public; reads the backend's own settings, so no copy of a price lives in this server)

search_us_numbers

Retail US phone plans for a handset, each with a buy_url

GET /mm/products?country=US

search_plans

Travel eSIM plans for a country, each with a buy_url

GET /mm/products?country=

get_quote

Price breakdown for one plan plus its buy_url

GET /mm/products/:id

How it works, example prompts, limits, troubleshooting and what is logged: meisimusa.com/claude-connector.html. search_plans and search_us_numbers take limit (default 10, max 50) and return currency once at the top level; get_quote takes an optional country_code to label a regional plan. The server also answers / (a one-page front door), /favicon.ico and /apple-touch-icon.png (the connector icon).

Nothing on that path opens an account, buys, tops up, texts, or reads an account, and any key sent with the request is ignored. Someone who wants a line goes to apply_url; someone who wants a plan opens its buy_url, which shows that exact plan on meisimusa.com (plans.html?buy=<plan_id>), where they pay by card. /mcp (full) and /mcp-info (ChatGPT) are unchanged. Locally: --directory / MEISIMUSA_DIRECTORY=1.

Configure

Env var

Default

Purpose

MEISIMUSA_API_KEY

none

Your API key (local stdio server). The remote server takes it per request from Authorization: Bearer, x-dealer-key or x-api-key and ignores this variable.

MEISIMUSA_API_BASE

https://meisimusa-backend.vercel.app

Backend base URL.

MEISIMUSA_TIMEOUT_MS

20000

Per-request timeout.

--mock / MEISIMUSA_MOCK=1

off

Deterministic in-memory data, no network.

--info-only / MEISIMUSA_INFO_ONLY=1

off

Only the retail discovery tools (the ChatGPT directory build). Remote: /mcp-info.

--directory / MEISIMUSA_DIRECTORY=1

off

The Claude Connectors Directory build: get_ai_line_offer plus the three catalog tools with a buy_url per plan. Remote: /mcp-directory (MCP_DIRECTORY_PATH).

MEISIMUSA_SITE_URL

https://www.meisimusa.com

Website used for buy_url.

PORT / MCP_PATH

8787 / /mcp

Remote HTTP server only.

Develop

npm install
npm run dev -- --mock     # stdio server on mock data
npm run start:http        # remote Streamable HTTP server
npm test                  # vitest: every tool, happy and error paths, against the mock
npm run build             # dist/ (enables npx + node dist/http-server.js)

Security

  • API keys, payment tokens and QR/LPA strings are never logged; identifiers are masked to first-4 + last-4.

  • The remote server never holds a key of its own; each request carries its caller's.

  • A backend 429 is surfaced as rate_limited with retry_after_seconds; a 402 as payment_required.

  • Messages are returned as received. The server parses nothing out of them.

Available Tools

16 tools
buy_numbersBuy US numbers (wallet)AInspect

Order new US phone numbers on your MeiSIM account, paid from its prepaid wallet. Prepaid: no returns, no refunds once a number is delivered. Choose billing "daily" (a minimum number of days paid now, then each day from the wallet) or "monthly" (a minimum number of months paid up front). A monthly order also says line_history: "fresh" or "any"; ask the user which. Call get_number_pricing first and tell the user the total. Numbers usually land within about 15 minutes; check with get_order. Safe to retry with the same customer_reference. Needs your API key.

Inputs: count (required), billing (required), days, voice, +5 more. Returns: note, voice, status, billing, +12 more

get_accountMy MeiSIM account and balanceA
Read-only
Inspect

Show the MeiSIM account behind your API key: company, status, prepaid wallet balance in USD, and how many new numbers you may still activate today. Use before buy_numbers, or when the user asks what is left. Needs your API key.

Inputs: no named parameters. Returns: email, status, company, currency, +4 more

get_activationGet activation QRA
Read-only
Inspect

Get the eSIM install QR code, activation (LPA) string, and status for an order. Pass the order_id from purchase. Status is "ready" when the profile can be installed (after the customer pays).

Inputs: order_id (required). Returns: status, expires_at, activation_code, qr_code_png_base64, +1 more

get_ai_line_offerGet the AI phone-line offerA
Read-only
Inspect

MeiSIM's current offer for real US phone lines used by AI agents: the monthly price per number for texts, and for texts plus voice over SIP; the first-term minimum; what a line includes (a real US mobile number on a national carrier, inbound texts to a webhook or over the API, voice over SIP with the number as caller ID, one call at a time, outbound calls to US numbers only); delivery time; payment methods; the lower price per line for more lines and who to write to from 1,000 lines; and links to apply and to the API docs. For people building voice agents, phone assistants, companion apps or SMS customer service who ask what a line costs, what it includes or how to get one. Takes no input. Read-only: it cannot open an account or order a line.

Inputs: no named parameters. Returns: monthly, product, currency, delivery, +13 more

get_number_pricingPrice of a new numberA
Read-only
Inspect

Show what a new US number costs on your MeiSIM account and whether you can order: the daily rate (minimum days, one-time activation fee, how many are ready right now) and the monthly rate (first month, renewals, minimum months), with and without voice. Call before buy_numbers. Needs your API key.

Inputs: no named parameters. Returns: daily, reason, monthly, currency, +3 more

get_orderCheck a number orderA
Read-only
Inspect

Check a number order from buy_numbers: status (provisioning, partially_fulfilled, fulfilled, delayed, cancelled, closed_refunded), the numbers delivered so far and what was charged. Pass the order_id or your customer_reference. Needs your API key.

Inputs: order (required). Returns: voice, status, billing, numbers, +10 more

get_quoteGet a price quoteA
Read-only
Inspect

Confirm the current USD price for a specific eSIM plan before purchasing. Returns the full plan plus a price breakdown and a short-lived quote. Call after search_plans, before purchase.

Inputs: plan_id (required). Returns: plan, total, buy_url, how_to_buy, +1 more

list_my_numbersList my numbersA
Read-only
Inspect

List the US phone numbers on your MeiSIM account: number, status, whether it has voice, how it is billed and the date it is paid through. Paged; pass next_offset to continue. Needs your API key.

Inputs: limit, offset, search. Returns: note, total, numbers, incoming, +1 more

purchasePurchase an eSIM or US numberAInspect

Begin buying an eSIM plan. Returns a secure Stripe payment link the customer opens to pay with their own card; the eSIM + QR are emailed automatically once payment clears. Poll get_activation with the returned order_id to fetch the QR. Safe to retry with the same idempotency_key.

Inputs: plan_id (required), customer_email (required), payment_method, billing_country, +1 more. Returns: error, status, message, order_id, +4 more

read_messagesRead received textsA
Read-only
Inspect

Read the text messages received on your MeiSIM numbers, newest first. Filter to one number and/or to messages after a timestamp. To follow a conversation, pass the received_at of the last message you saw as since. Needs your API key.

Inputs: limit, since, number. Returns: note, count, messages, newest_received_at

search_plansSearch travel eSIM plansA
Read-only
Inspect

Search travel eSIM data plans for a destination country. Returns plans with data allowance, validity in days, and USD price. Use this first when a user wants mobile data for a trip (e.g. "5GB in Italy for 10 days"). Returns a plan_id to pass to get_quote / purchase.

Inputs: country_code (required), duration_days (required), data_gb, sort_by. Returns: meta, plans, how_to_buy

search_us_numbersSearch US phone-number plansA
Read-only
Inspect

Find real US phone-number plans (a genuine US carrier line with calls, texts, and data, no SSN or contract). Use this when the user wants an actual US number, not just travel data. Returns a plan_id for purchase.

Inputs: max_price_usd. Returns: meta, plans, how_to_buy

send_messageSend a textAInspect

Send a text message from one of your MeiSIM numbers to a US number. Sending must be enabled on your account and each number has a monthly allowance; a refusal tells you which. The answer means accepted by the carrier: a mobile line has no delivery receipt. The same text to more than three numbers from one line inside an hour is refused (carriers drop that as a broadcast); write to each person in their own words. Not for emergency services. Needs your API key.

Inputs: to (required), from (required), message (required). Returns: to, from, note, sent

topup_lookupLook up a line to top upA
Read-only
Inspect

Look up an existing US prepaid line (by phone) or an eSIM (by ICCID / order) and list the top-up plans available for it. Returns product_ids to pass to topup_start.

Inputs: line_type (required), email, iccid, phone, +1 more. Returns: hint, lines

topup_startStart a top-upAInspect

Start a top-up/recharge for an existing line or eSIM, using a product_id from topup_lookup. Returns an order_id and a payment URL where the customer completes payment. For range plans, pass custom_amount.

Inputs: line_type (required), product_id (required), customer_email (required), iccid, +4 more. Returns: error, amount, status, message, +4 more

wait_for_messageWait for the next textA
Read-only
Inspect

Wait for the next text message on one of your MeiSIM numbers and return it. Blocks up to timeout_seconds (default 30, max 50). Pass since as the time you started waiting (default: now) so an older message is not mistaken for the new one. If nothing arrives, received is false; call again to keep waiting. Needs your API key.

Inputs: since, number, timeout_seconds. Returns: note, since, messages, received, +1 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 16 tools

    Disambiguation3/5

    Messaging tools (read_messages vs wait_for_message) and top-up tools (topup_lookup vs topup_start) are clearly delineated, but the purchase surface has three adjacent paths: search_us_numbers returns a plan_id 'for purchase', while purchase is described as buying an 'eSIM plan', and buy_numbers separately orders numbers from the prepaid wallet. Pricing is similarly split between get_number_pricing (own account) and get_ai_line_offer (public offer), and search_plans vs search_us_numbers sit close together. Descriptions cross-reference well enough to recover, but an agent can easily misselect on the buying flow.

    Naming Consistency4/5

    Almost everything is snake_case verb_noun (get_order, list_my_numbers, send_message, read_messages), which is predictable and readable. The exceptions are the bare verb 'purchase' and the noun-first prefix family topup_lookup/topup_start, which break the verb_noun pattern slightly without causing confusion.

    Tool Count4/5

    Sixteen tools is slightly heavy but the domain genuinely spans four areas: travel eSIM data, US number provisioning, top-ups, and SMS messaging plus account/pricing reads. Each tool maps to a real operation with few obvious redundancies, so the count is defensible rather than bloated.

    Completeness4/5

    The main lifecycle chains are covered end to end: search_plans -> get_quote -> purchase -> get_activation, get_number_pricing -> buy_numbers -> get_order -> list_my_numbers, and topup_lookup -> topup_start, plus a read/send/wait messaging trio. Gaps remain around lifecycle exits and recovery: there is no cancel-order or release-number operation, and no 'list my eSIM orders' tool, so an agent that loses an order_id has a dead end for retrieving the activation QR.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers