Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for the remote HTTP server only.8787
MCP_PATHNoPath for the remote HTTP server only./mcp
MEISIMUSA_MOCKNoSet to 1 to use deterministic in-memory data with no network. Equivalent to the --mock flag.0
MEISIMUSA_API_KEYNoYour API key for the local stdio server. Optional: without a key, the retail tools still work and the number tools answer with where to apply.
MCP_DIRECTORY_PATHNoPath used for the remote Claude Connectors Directory build.
MEISIMUSA_API_BASENoBackend base URL.https://meisimusa-backend.vercel.app
MEISIMUSA_SITE_URLNoWebsite used for buy_url.https://www.meisimusa.com
MEISIMUSA_DIRECTORYNoSet to 1 to use the Claude Connectors Directory build: get_ai_line_offer plus the three catalog tools with a buy_url per plan. Equivalent to the --directory flag.0
MEISIMUSA_INFO_ONLYNoSet to 1 to expose only the retail discovery tools (the ChatGPT directory build). Equivalent to the --info-only flag.0
MEISIMUSA_TIMEOUT_MSNoPer-request timeout in milliseconds.20000

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_plansA

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.

get_quoteA

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.

get_ai_line_offerA

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.

search_us_numbersA

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.

purchaseA

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.

get_activationA

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).

topup_lookupA

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.

topup_startA

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.

get_accountA

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.

get_number_pricingA

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.

buy_numbersA

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.

get_orderA

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.

list_my_numbersA

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.

read_messagesA

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.

wait_for_messageA

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.

send_messageA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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