Give your AI agent the inbox.
The nativeMsg MCP server connects your AI tools directly to nativeMsg: Claude, ChatGPT, or anything that speaks MCP. Describe what you want, and your agent builds, sends, and manages branded RCS experiences, right from the chat.
https://mcp.nativemsg.com/mcpBuild a storefront for our three best sellers, with a Shop now button on each, and reply to ORDER with tracking.
One URL, every assistant. nativeMsg speaks MCP, the open standard, so it works with the AI tools your team already uses, and the ones that don't exist yet.
Most messaging MCPs send a message. Ours runs the whole experience.
Other platforms hand your AI a pipe. nativeMsg hands it the full RCS stack: your agent designs the conversation itself, sends from your verified brand, and runs it all with the account tools built in. One connection, no carrier integration to build.
Build complete RCS experiences
Describe it and your agent builds it: a storefront, a booking flow, a lead-gen campaign, an order tracker. Conversations with branching, data capture, and live connections to your own systems, all versioned so every change can be rolled back.
Send rich, branded RCS
Your agent sends interactive messages from your verified brand, with automatic SMS fallback when a device doesn't support RCS.
Run inbound and outbound
Answer the customers who text you first and reach the ones who should hear from you. Your agent runs two-way conversations, then schedules and triggers broadcasts.
Manage your account
Keep the details in order without leaving the chat. Your agent manages channels, contacts, tags, and templates, and checks whether a number can receive RCS before it sends.
Connect in about two minutes.
No API keys to copy, no SDK to install. Paste one URL into your AI tool and sign in with your nativeMsg account.
Copy the server URL
https://mcp.nativemsg.com/mcp
Add it to your AI tool
Add it as a custom connector or remote MCP server in Claude, Claude Code, or any client that supports remote MCP.
Sign in with nativeMsg
Approve access with your nativeMsg login. Your agent only gets the permissions you grant.
Add nativeMsg as a custom connector and paste the server URL. You'll be asked to sign in with your nativeMsg account.
https://mcp.nativemsg.com/mcpAdd nativeMsg as a remote MCP server, then sign in when prompted. From the terminal:
claude mcp add --transport http nativemsg https://mcp.nativemsg.com/mcpChatGPT, Cursor, and any other client that supports remote MCP servers can connect by adding the URL as a custom server or connector. The exact menu varies by tool.
https://mcp.nativemsg.com/mcpYou need a nativeMsg account to connect. Don't have one yet? Create a free account, then come back and connect.
Want the technical details?
The nativeMsg playbook covers the full API reference, message types, webhooks, and everything your agent can work with.
Describe it. Your agent builds it. Tap through it on your phone.
Once you're connected, just ask. A few prompts to start with:
"Build a booking experience: when someone texts BOOK, show our three services, capture their preferred time, and confirm with an add-to-calendar button."
"When someone texts ORDER, reply with quick replies for Track my order, Reorder, and Talk to support."
"Send a carousel of our three best sellers to my test phone, with a Shop now button on each."
"Tag everyone who tapped Reorder this week as repeat-buyer and schedule a thank-you offer for Friday at 10am."
"Before we send, check which numbers on this list can receive RCS and which will fall back to SMS."
Where AI meets your customers.
Your customers already talk to AI assistants all day. The nativeMsg MCP server lets your AI talk to them in the inbox they already use, with no app to download.
Run campaigns from the chat you already work in
Ask Claude to build a lead-gen experience, set up a promotion, segment your list, and schedule the send. No new dashboard to learn, and every message goes out from your verified brand.
Prototype messaging without wiring the API first
Use Claude Code to test sends, inspect templates, and check RCS capability while you build. When you're ready, the same platform is there through REST API and webhooks.
Give your agent a verified voice in the inbox
Agents stuck in email and web chat can reach customers in their messaging app, with rich interactive messages and two-way conversations that answer back.
Your agent sends real messages. So we built in guardrails.
OAuth 2.1 sign-in
Connect with your nativeMsg login. No API keys pasted into config files.
Scoped permissions
Your agent gets only the access you approve, and you can revoke it anytime.
Confirm before send
Your AI tool asks for your approval before anything reaches a customer.
Verified sender
Every RCS message carries your carrier-verified brand name and logo, with SMS fallback.
Versioned with rollback
Every change your agent makes to an experience is a saved revision. One click restores the previous version.