get_my_release_alerts — NetSendo website MCP Tool Read-only
get_my_release_alerts
(get my release alerts) is one of 10 tools on the
NetSendo website
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_my_release_alerts from your client
- Claude Code NetSendo website get_my_release_alerts run in your project directory
- Claude Desktop NetSendo website get_my_release_alerts ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NetSendo website get_my_release_alerts ~/.cursor/mcp.json
- VS Code NetSendo website get_my_release_alerts .vscode/mcp.json
- Zed NetSendo website get_my_release_alerts ~/.config/zed/settings.json
- Windsurf NetSendo website get_my_release_alerts ~/.codeium/windsurf/mcp_config.json
- Cline NetSendo website get_my_release_alerts ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NetSendo website get_my_release_alerts ~/.gemini/settings.json
- Grok NetSendo website get_my_release_alerts .mcp.json (in your project root)
- ChatGPT NetSendo website get_my_release_alerts Settings → Connectors → Advanced → Developer mode
- Claude.ai NetSendo website get_my_release_alerts Settings → Connectors → Add custom connector
- LangChain NetSendo website get_my_release_alerts pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http website https://netsendo.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.