NetSendo v2.10.0: Connect Claude & AI Apps via Remote MCP

AI assistants can now do real work, but connecting them to your marketing stack has been awkward. You had to create an API key, paste it into a config file, install Node.js locally and hope the key didn't leak. For a self-hosted platform that's built around data ownership, that wasn't good enough.

NetSendo v2.10.0 fixes this. Every installation now serves its own remote MCP endpoint at https://<your-domain>/mcp. Paste that address into Claude, ChatGPT, Cursor, Hermes Agent or another MCP host, sign in to NetSendo and pick which permissions to grant. The assistant then works with your lists, subscribers and messages through the same 140 tools as the npm MCP client.

🚀 What's New in v2.10.0

The AI Connector: Like a "Sign in with…" Button for Your Assistant

You've probably used "Sign in with Google" on a website. The AI connector works the same way in reverse: the AI app asks to sign in to your NetSendo. When you add the connector, the app redirects you to your installation. You log in, see what the app wants to do, and approve it.

The sign-in screen shows:

• The app's name and identity status: confirmed (Claude's published identity is), self-declared, or a warning if the app is published on one site but returns to another
• Which NetSendo account is signed in, so you don't approve the wrong one
• Requested permissions with checkboxes, such as lists:read, subscribers:write and messages:write. You can grant fewer than the app asks for.

Settings → AI Connector

This new page shows your installation's connector address, the list of connected apps with a Disconnect button (it takes effect on the next request), and step-by-step instructions for Claude, Claude Code, Hermes Agent, ChatGPT, Cursor, VS Code, Gemini CLI and hosts that only run local commands. The instructions are available in Polish, English, German and Spanish.

For example, in Claude Code:

claude mcp add --transport http netsendo https://your-domain.com/mcp

Built on the Standards MCP Hosts Expect

• ✅ OAuth authorization code flow with PKCE
• ✅ Client ID Metadata Documents and dynamic client registration
• ✅ Refresh tokens that are replaced on every use, plus token revocation
• ✅ Discovery documents under /.well-known/
• ✅ One-hour access tokens. Apps unused for 90 days must sign in again.
• ✅ Only hashes of tokens are stored

ℹ️ Note: If a host can't do OAuth sign-in, it can call /mcp with a regular NetSendo API key in the Authorization: Bearer header. API keys, the REST API and the local @netsendo/mcp-client work as before.

{
  "mcpServers": {
    "netsendo": {
      "url": "https://your-domain.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_NETSENDO_API_KEY" }
    }
  }
}

The exact config format depends on the host. Check your AI app's documentation.

Fair Use Limits

No single app can monopolize your server. Each app may send 120 requests per minute and run two tool calls at once, with a cap of three concurrent calls across all apps. A call over the limit gets a "busy, call again" response, and the assistant retries on its own. You can change these limits in .env.

💼 Benefits & Use Cases

🛠️ Step-by-Step Guide

1. Update NetSendo

   docker compose pull && docker compose up -d

   The migration adds four tables: connector_clients, connector_connections, connector_tokens and connector_auth_codes. A daily connector:prune task removes expired codes, tokens and connections.

2. Check that your installation is reachable over public HTTPS

   Cloud apps like Claude connect from their provider's servers, so localhost or a VPN-only address won't work. The bundled nginx config needs no changes.

3. Open Settings → AI connector

   Copy your /mcp address and follow the instructions for your AI app.

4. Approve the app

   On the sign-in screen, check the identity status and the signed-in account, then untick any permissions the app doesn't need.

5. Optional: enable compressed assets

   Get the new docker/nginx/default.conf and restart the webserver container:

   docker compose restart webserver

⚠️ Important: The connector is on after the update. It answers at /mcp, /oauth/* and /.well-known/oauth-*, but does nothing until someone signs in and approves an app. To turn it off, set the following and restart the containers:

MCP_CONNECTOR_ENABLED=false

Common Pitfalls

• Claude can't connect: Your installation probably isn't reachable from the internet over HTTPS, or a reverse proxy is blocking /.well-known/. See docs/MCP_CONNECTOR.md for proxy notes and troubleshooting.
• Custom Docker images: Add the two new steps from docker/php/Dockerfile. One builds the MCP tools under /opt/netsendo-mcp, and the other creates the .gz files of built assets.
• Assets still uncompressed: If a proxy talks HTTP/1.0 to NetSendo's nginx, replace default.conf or let the proxy compress the assets itself.

⚡ Performance: A Much Lighter Panel

• The first load is about a quarter of its old size. Previously, every page bundled all four interface languages into a 1.85 MB start-up script. Now it's 0.42 MB of script plus about 0.36 MB of texts for the active language only. English, the fallback language, is fetched only when a text is actually missing.
• Guests no longer prefetch the whole panel. Prefetching 286 files (7.7 MB) now happens only for signed-in users. The sign-in page went from about 250 requests and 9 MB to 15 requests and 1.2 MB.
• Pre-compressed assets: Every built script and style ships with a ready .gz file. Files under /build/assets/ are cached for a year as immutable.

Other Changes

• The application image now includes the MCP tools (/opt/netsendo-mcp) and runs them with the Node.js that's already in the image.
• mcp/dist was rebuilt from the current source, so send_sms now passes the SMS text correctly. The npm package @netsendo/mcp-client 1.6.0 is unchanged by this release.
• The page's lang attribute now updates when you switch languages.

🎉 Conclusion

NetSendo v2.10.0 connects your self-hosted marketing platform to modern AI assistants, and you keep control. There are no keys to copy, each app gets only the permissions you choose, each user's data stays separate, and your data stays on your server. The panel is also much faster to load.