update_custom_provider — OutageDeck MCP Tool Mutating
update_custom_provider
(update custom provider) is one of 14 tools on the
OutageDeck
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call update_custom_provider from your client
- Claude Code OutageDeck update_custom_provider run in your project directory
- Claude Desktop OutageDeck update_custom_provider ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor OutageDeck update_custom_provider ~/.cursor/mcp.json
- VS Code OutageDeck update_custom_provider .vscode/mcp.json
- Zed OutageDeck update_custom_provider ~/.config/zed/settings.json
- Windsurf OutageDeck update_custom_provider ~/.codeium/windsurf/mcp_config.json
- Cline OutageDeck update_custom_provider ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI OutageDeck update_custom_provider ~/.gemini/settings.json
- Grok OutageDeck update_custom_provider .mcp.json (in your project root)
- ChatGPT OutageDeck update_custom_provider Settings → Connectors → Advanced → Developer mode
- Claude.ai OutageDeck update_custom_provider Settings → Connectors → Add custom connector
- LangChain OutageDeck update_custom_provider pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http outagedeck-status https://outagedeck.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.