Versioning Policy
The SuprSend MCP server follows Semantic Versioning (SemVer). For example, in version 0.5.13, 0 is the major, 5 is the minor, and 13 is the patch. Major. Changes that aren’t backward compatible, such as renaming or removing a tool, or changing a tool’s inputs in a way that breaks existing calls. Minor. New capabilities that are backward compatible, such as new tools or new optional inputs. For example, 0.5.0 addedworkflows_diff, templates_diff and workflows_list_versions.
Patch. Backward-compatible fixes and small improvements, such as clearer tool descriptions, better error messages and security fixes.
How updates reach you
The server is hosted, so there’s nothing to install or upgrade. Every client connected tohttps://mcp.suprsend.com/mcp uses the latest version as soon as it’s released, and you can’t pin an older one.
A new version can change the tools your agent sees, such as a new tool or a clearer description. The server doesn’t notify clients when its tools change, so your client sees the change once it loads the tool list again, usually when you start a new chat or reconnect the SuprSend connector.
Each release is also published to the official MCP Registry as com.suprsend/mcp.
Check which version you’re on
The server reports its name (suprsend) and version when your client connects. Clients that show server details, such as the MCP Inspector, display it. The changelog lists what changed in each version.
MCP spec support
The server is built for MCP specification 2026-07-28. Clients that still use the 2025 protocol also connect and get the same tools. They don’t get the skills methods (skills/list and skills/get), which only exist in the 2026 spec, so they can read the skills with docs_get_skill instead. A client that supports both versions uses 2026.
Tool names
Tools are named<group>_<action>, such as users_get. The older dotted names, such as users.get, still work in ?tools= filters, so connector URLs saved with them keep working. See Scope the connection.