nativeMsg MCP server
Yes. nativeMsg publishes an official MCP server at https://mcp.nativemsg.com/mcp. It's hosted. It offers 53 tools. We last checked it on 22 Nov 2026.
Official: answers MCP requests at mcp.nativemsg.com, on nativeMsg's own domain nativemsg.com. Checked 22 Nov 2026. Maintained by Stuart Brameld.
Key facts
As of 22 Nov 2026, nativeMsg's official MCP server scores 55/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 53 tools.
How the Agent Readiness Index works · Wrong? Suggest a correction
nativeMsg MCP server review
55/100
nativeMsg's MCP server scores 55/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.
The good
Hosted by nativeMsg: connect by URL, with nothing to install
Published to the official MCP Registry
Answered 100% of our checks in the last 90 days
The bad
Nothing we've found.
Not checked yet: how you sign in; a docs page listing its tools; what agent access costs. Anything not checked scores nothing.
Official MCP server
nativeMsg MCP server
- Address
- https://mcp.nativemsg.com/mcp
- Runs
- Hosted
- Sign-in
- Official MCP Registry
-
Listed as
com.nativemsg/mcp· published 12 Nov 2026 - How we know it's official
-
- Answers MCP requests at mcp.nativemsg.com, on nativeMsg's own domain nativemsg.com.
- Tools
- 53 tools · listed 21 Oct 2026
- First seen
- 1 Oct 2026
- Last checked
-
Reachable ·
16 Nov 2026: reachable17 Nov 2026: reachable18 Nov 2026: reachable19 Nov 2026: reachable20 Nov 2026: reachable21 Nov 2026: reachable22 Nov 2026: reachable
- Uptime
- 100% · 55 of 55 checks reachable since 1 Oct 2026
nativeMsg MCP server tools (53)
As the server lists them. Names and descriptions are the vendor's own.
-
list_channel_typesList every messaging channel type supported by nativeMsg. Returns an array of `{ name, description }`. Channel-type ids include `rcs`, `dlc`, `dsc`, `fb`, `twr`, `alx`, `web`, `bmp`. Used as the `channelType` field on channel-creation calls.
-
check_rcs_capabilityCheck whether a phone number supports RCS, and which RCS features. Returns `{ rbmEnabled: bool, features: string[], name: string|null }`. Features include codes like `RICHCARD_STANDALONE`, `ACTION_DIAL`, `ACTION_OPEN_URL`, `RICHCARD_CAROUSEL`. Pass `channel_id` to scope the check to a specific RCS channel; omit to use the account default.
-
lookup_phone_capabilityCarrier and line-type metadata for any phone number. Returns `{ callingCountryCode, countryCode, carrierName, mobileCountryCode, lineType, format, phoneNumber, valid, validationErrors }`. `lineType` is one of: landline, mobile, fixedVoip, nonFixedVoip, personal, tollFree, premium, sharedCost, uan, voicemail, pager, unknown.
-
list_channelsList every messaging channel configured in the account. A channel represents a connection to one messaging destination (RCS agent, SMS short/long code, Facebook page, web chat, etc.). The returned objects carry `id`, `channelType` (e.g. 'rcs', 'dlc', 'fb', 'web'), `botId`, `name`, and `description`. Pass `bot_id` to filter to channels for a single bot.
-
get_channelFetch one channel's full details by id.
-
get_channel_subscription_countGet the number of humans currently subscribed to a channel. Returns `{ channelId, subscribedHumansCount }`.
-
subscribe_humans_to_channelBulk subscribe humans to a channel. Subscribed humans become eligible to receive messages sent to that channel. Returns `{ channelId, subscribedHumansCount }`.
-
unsubscribe_humans_from_channelBulk unsubscribe humans from a channel. Returns `{ channelId, unsubscribedHumansCount }`.
-
add_humans_by_phonesBulk-create humans on a channel by phone number; optionally tag/subscribe.
-
add_tester_deviceRegister a phone as a tester device on an RCS channel. An RCS agent that has not launched can only message its tester devices. Registering sends the device an invitation it must accept before messages are delivered to it; a human for the phone is also created on the channel.
-
list_humansList every human (end-user / contact) in the connected nativeMsg account. Returns a JSON array of human objects with fields including `id`, `name`, `firstName`, `lastName`, `phoneNumber`, `email`, `botEnabled`, `channels`, `subscribedChannels`, and `customFields`. No pagination is documented; large accounts may return many records. Use `find_humans_by_attributes` to filter, or `get_human` for a single record.
-
get_humanFetch a single human by id. Returns the full human object including channels, subscriptions, custom fields, RCS capability flags, and bot-enabled state.
-
find_humans_by_attributesFind humans whose custom attribute matches a predicate. Wraps `GET /humans?filters=...` for the common single-condition case. `operator` is one of: present, absent, equal, notEqual, greater, greaterOrEqual, less, lessOrEqual. The `value` argument is required for all operators except `present` and `absent`. Note: type mismatches (e.g. a numeric operator against a string attribute) silently match nothing — they do not raise an error.
-
get_human_subscriptionGet a human's channel-subscription status. Returns `{ channelId, humanId, subscription: bool }` for the human's primary channel.
-
get_human_tagsList the tags currently assigned to a human. Returns an array of tag objects: `{ id, name, description, dateCreated, dateUpdated }`.
-
assign_tags_to_humanAssign one or more tags to a human. Provide exactly one of `tag_names` (assign by name; names that don't exist will be created) or `tag_ids` (assign by existing tag id). Returns `{ code, message }`.
-
unassign_tags_from_humanRemove one or more tags from a human. Provide exactly one of `tag_names` or `tag_ids`. Returns `{ code, message }`.
-
update_human_attributesAdd or update arbitrary custom attributes on a human.
-
set_human_bot_enabledEnable or disable the conversational bot for a single human. When disabled, the bot stops responding automatically in that human's conversation — useful when a human agent has taken over. Returns the full updated human object.
-
send_rcs_text_messageSend a plain-text RCS message to one or more humans. NON-REVERSIBLE. Delivers an actual SMS/RCS message and may incur per-message charges. Confirm with the user before calling.
-
send_rcs_media_messageSend an image / audio / video / file RCS message. NON-REVERSIBLE.
-
send_rcs_buttons_messageSend an RCS message with action buttons (suggested actions). NON-REVERSIBLE.
-
send_rcs_quick_replies_messageSend an RCS message with tap-to-reply chips (quick replies). NON-REVERSIBLE. Quick replies are short text chips the user taps to reply with a pre-filled message. Up to 11 replies.
-
send_rcs_carousel_messageSend an RCS swipeable carousel of cards. NON-REVERSIBLE.
-
send_rcs_rich_card_messageSend an RCS rich card (single card with media + suggestions). NON-REVERSIBLE.
-
send_rcs_list_messageSend an RCS list message (sectioned list of items). NON-REVERSIBLE.
-
send_message_from_templateSend a saved message template to one or more humans. NON-REVERSIBLE.
-
schedule_text_messageSchedule a plain-text RCS message to send later. NON-REVERSIBLE. Wraps `POST /v1/messages?scheduledDate=...&misfireType=...` for the most common scheduling case. For scheduled sends of richer payloads (carousel, rich-card, etc.), use the dashboard or open a request — see TODO.md.
-
get_message_statusLook up delivery status for every message produced by a send request. Pass the `requestId` returned by a send-message tool. A single send may fan out to many recipients (one row per recipient). Each row carries `id`, `humanId`, `channelId`, `status` (single-letter code: A=Accepted, P=Pending, S=Sent, D=Delivered, F=Failed, Q=Queued, R=Read), `messageType` (O=Outbound, I=Inbound, B=Blast), `delivered`, and the original `message` payload.
-
get_messageFetch a single message row by its numeric message id. Use `get_message_status` first if you only have a `requestId`.
-
list_botsList every conversational bot configured in the account. A bot is a scripted conversation flow attached to one or more channels. Returned objects include `id`, `name`, `interactions` (the bot's flow definition — large nested object), `dateCreated`, `currentRevision`, and `latestRevision`.
-
get_botFetch one bot by id, including its full interactions tree.
-
list_blastsList every blast (saved broadcast) in the account. A blast is a reusable broadcast definition created in `draft` status and sent via the messages endpoint. Returned objects carry `id`, `title`, `message`, `bot`, `channels`, `tags`, `recipientsNumber`, `status` (`draft`/`sent`/`scheduled`/`processing`), and `sendingProgress`.
-
get_blastFetch one blast by id with its message body, schedule, and status.
-
get_blast_recipientsList the humans targeted by a blast, with per-recipient delivery status.
-
get_blast_recipients_countCount of recipients for a blast (useful before sending to confirm scope). Shape varies by blast status: `draft`/`scheduled`/`sent` returns a single integer; `processing` returns per-status counts (read/pending/queued/ accepted/delivered/failed/sent/total).
-
get_blast_tagsList the tags assigned to a blast (used to derive its recipients).
-
get_blast_channelsList the channels through which a blast will be sent.
-
send_blastTrigger a saved blast to send immediately. NON-REVERSIBLE. Once a blast is sent it cannot be unsent. Confirm the blast's recipient scope with `get_blast_recipients_count` before calling. Wraps `POST /v1/messages` with `{ blastId }`. Returns: `{ requestId }` — pass to `get_message_status` to track delivery.
-
schedule_blastSchedule a saved blast to send at a future time. NON-REVERSIBLE once it fires. Use `cancel_blast_schedule` to cancel before it fires.
-
cancel_blast_scheduleCancel a scheduled (not-yet-fired) blast. Has no effect on blasts that have already fired or been sent. Returns `{ code, message }`.
-
assign_blast_tagsReplace the set of tags on a blast (REPLACE SEMANTICS). All previously assigned tags are removed first, then the new set is applied. Pass empty/None for both args to clear all tags. The blast's recipients are recomputed as the intersection of (humans with any of the tags) and (humans subscribed to the assigned channels).
-
assign_blast_channelsReplace the set of channels on a blast (REPLACE SEMANTICS). All previously assigned channels are removed and replaced by `channel_ids`. Pass an empty list to unassign all channels.
-
list_tagsList every tag defined in the account. Returns an array of `{ id, name, description, dateCreated, dateUpdated }`.
-
get_tagFetch a single tag by id.
-
list_tags_for_humansList the tags assigned to a set of humans, grouped by human. Wraps `GET /tags?humanIds=...`. Useful for bulk lookups instead of calling `get_human_tags` per id.
-
list_humans_by_tagList every human carrying a given tag.
-
list_message_templatesList every message template available in the account. Templates are saved Message Object payloads that can be sent via the messages endpoint with a `templateId`. Returned objects include `id`, `name`, `data` (the saved Message Object), `readOnly` (true = system template), `dateCreated`, and `dateUpdated`.
-
get_message_templateFetch a single message template by id, including its full payload.
-
list_webhooksList every webhook receiver registered on the account.
-
get_webhookFetch one webhook by id, including its url and event subscriptions.
-
list_integrationsList every third-party integration configured on the account.
-
get_integrationFetch one integration by id.
Connect your AI to nativeMsg
Add the official nativeMsg MCP server to Claude, ChatGPT or your editor.
Connect nativeMsg MCP to Claude
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it nativeMsg, paste the address below and click Add.
Connect nativeMsg MCP to ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it nativeMsg and paste the address below.
ChatGPT usually only connects to servers with self-serve sign-in or none.
Connect nativeMsg MCP to Cursor
Opens Cursor if it's installed. If nothing happens, use the JSON below.
Connect nativeMsg MCP to VS Code
Opens VS Code if it's installed. Otherwise add the JSON settings from the Cursor tab to your .vscode/mcp.json.
nativeMsg MCP server questions
Does nativeMsg have an official MCP server?
Yes. nativeMsg publishes its MCP server itself. Its address is on nativeMsg's own domain (mcp.nativemsg.com). MartechDB only lists servers a vendor publishes, never community copies.
What is the nativeMsg MCP server URL?
The address is https://mcp.nativemsg.com/mcp.
How do I connect nativeMsg MCP to Claude, ChatGPT or Cursor?
In Claude, add https://mcp.nativemsg.com/mcp as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http nativemsg https://mcp.nativemsg.com/mcp
What can the nativeMsg MCP server do?
It offers 53 tools, including list_channel_types, check_rcs_capability, lookup_phone_capability, list_channels and get_channel (as listed on 21 Oct 2026).
Is the nativeMsg MCP server in the official MCP Registry?
Yes, as com.nativemsg/mcp.
Is the nativeMsg MCP server working?
Yes. It answered our most recent check. We last checked it on 22 Nov 2026.
What are the alternatives to nativeMsg's MCP server?
In SMS, WhatsApp & push, the most agent-friendly alternatives with an official MCP server are Omnisend (100/100), Respond.io (97/100), Privy (94/100), Aimtell (94/100) and OneSignal (91/100). nativeMsg scores 55/100 on the same index.
Alternatives to nativeMsg's MCP server
Vendors in SMS, WhatsApp & push with an official MCP server, the most agent-friendly first. nativeMsg scores 55/100.
Omnisend
omnisend.com
Respond.io
respond.io
Privy
privy.com
Aimtell
aimtell.com
OneSignal
onesignal.com
Change history
What we've seen change for nativeMsg, newest first.
-
nativeMsg: nativeMsg MCP server added to the official MCP Registry
-
nativeMsg: nativeMsg MCP server: 1 tool added (now 53)
Use with AI
Connect your AI to MartechDB
Then ask it about nativeMsg, or any of the 1,851 marketing tools with an official MCP server. Free, no sign-in.
Claude.ai and Claude Desktop
Open Customize, then Connectors.
Click +, then Add custom connector.
Name it MartechDB, paste the address below and click Add. There's no sign-in.
The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.
Claude Code
Run this in your terminal:
ChatGPT
Open Settings, then Apps, then Advanced settings.
Turn on Developer mode, then click Create.
Name it MartechDB, paste the address below and choose No authentication.
Developer mode is on Plus and Pro plans, and on Business, Enterprise and Edu if an admin allows it.
API
The same data as JSON, with no sign-in. See the OpenAPI description for every endpoint and field.
CLI
Search the directory and print the command to connect a vendor's server, from your terminal. Needs Node 18 or later. View on npm
Show that your MCP server is verified
If you work at nativeMsg, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.
Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.