Search / com.msg91.mcp/mcp
protogridR0· no sign-inFind and call the right MSG91 API for SMS, OTP, WhatsApp, Email and Voice.
v1.0.0 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://mcp.msg91.com/mcp"
}
}
}claude mcp add --transport http mcp https://mcp.msg91.com/mcp[mcp_servers.mcp]
url = "https://mcp.msg91.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcp": {
"type": "remote",
"url": "https://mcp.msg91.com/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://mcp.msg91.com/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLm1zZzkxLmNvbS9tY3AifQ%3D%3D"
}{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.msg91.com/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"httpUrl": "https://mcp.msg91.com/mcp"
}
}
}extensions:
"mcp":
enabled: true
name: "mcp"
type: streamable_http
uri: "https://mcp.msg91.com/mcp"
timeout: 300
protocol.modernprotocol.statelessprotocol.transportprotocol.list_ttlauth.prm, auth.as_metadata, auth.cimdauth.secret_in_urltools.descriptionstools.description_lengthtools.schemastools.annotationstools.directory_hintstools.token_costtools.api_dumptools.hidden_textstability.changesstability.rug_pullstability.new_linksdeps.known_vulns, deps.mcp_sdk_version, deps.resolvablecall_any_read_api_of_msg91removedRead from any MSG91 API endpoint with a GET request for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For POST, PUT, PATCH and DELETE use call_any_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, and query params in `query` (not in the url). For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.
call_any_api_of_msg91removedSend a POST, PUT, PATCH or DELETE request to any MSG91 API endpoint for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For GET requests use call_any_read_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, query params in `query` (not in the url) and the JSON body in `body`. For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.
call_any_read_api_of_msg91addedRead from any MSG91 API endpoint with a GET request for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For POST, PUT, PATCH and DELETE use call_any_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, and query params in `query` (not in the url). For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.
call_any_api_of_msg91addedSend a POST, PUT, PATCH or DELETE request to any MSG91 API endpoint for the user and return its response. Use it once you know the exact endpoint: look it up with get_msg91_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-msg91 skill first: it explains which tool to use when. For GET requests use call_any_read_api_of_msg91. Pass the full url with path variables filled in, the headers the docs list, query params in `query` (not in the url) and the JSON body in `body`. For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.
Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +dns-namespace +website +reachable +uptime-100% +updated-15d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://mcp.msg91.com/mcp streamable-http | none | yes | 100% | 1455 ms | 2025-11-25 | 2026-11-14 |
get_msg91_api_docsread-only | Browse the MSG91 API docs, one level at a time. Call it without arguments to get the top level: the modules and pages with a short description and the endpoints they hold. Call it with `path` set to a module's or page's link (or path) to get what is inside it; each listing links the next level. Call it with `path` set to an endpoint's link ending in ".openapi.yml" to get that endpoint as an OpenAPI file: method, url, headers, query params, path variables, a request body example and sample responses. Fetch only the level you need. |
quickstart-msg91read-only | Quickstart for the MSG91 API Call this to load the full instructions for this skill before doing the task. |
search_msg91_docsread-only | Search the MSG91 documentation with a natural-language question. Returns the most relevant passages with their page URLs. |
Schemas: list_tools.
{
"name": "com.msg91.mcp/mcp",
"icons": [
{
"src": "https://stuff.thingsofbrand.com/msg91.com/images/imge_msg91.svg",
"sizes": [
"any"
],
"mimeType": "image/svg+xml"
}
],
"title": "MSG91",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://mcp.msg91.com/mcp",
"type": "streamable-http"
}
],
"version": "1.0.0",
"repository": {
"url": "https://github.com/walkover-mcp/msg91",
"source": "github"
},
"websiteUrl": "https://msg91.com",
"description": "Find and call the right MSG91 API for SMS, OTP, WhatsApp, Email and Voice."
}