update_channel — Bisque Presentations MCP Tool Mutating
update_channel
(update channel) is one of 19 tools on the
Bisque Presentations
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call update_channel from your client
- Claude Code Bisque Presentations update_channel run in your project directory
- Claude Desktop Bisque Presentations update_channel ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bisque Presentations update_channel ~/.cursor/mcp.json
- VS Code Bisque Presentations update_channel .vscode/mcp.json
- Zed Bisque Presentations update_channel ~/.config/zed/settings.json
- Windsurf Bisque Presentations update_channel ~/.codeium/windsurf/mcp_config.json
- Cline Bisque Presentations update_channel ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bisque Presentations update_channel ~/.gemini/settings.json
- Grok Bisque Presentations update_channel .mcp.json (in your project root)
- ChatGPT Bisque Presentations update_channel Settings → Connectors → Advanced → Developer mode
- Claude.ai Bisque Presentations update_channel Settings → Connectors → Add custom connector
- LangChain Bisque Presentations update_channel pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http presentations https://bisque.cloud/presentations/mcpOther tools on this server
- get_presentation_spec
- create_presentation
- publish_narrated_presentation
- get_presentation_status
- list_presentations
- get_presentation_analytics
- get_presentation_context
- create_artifact
- list_artifacts
- get_artifact
- update_artifact
- share_artifact
- delete_artifact
- list_artifact_threads
- get_artifact_thread
- create_artifact_thread
- reply_to_artifact_thread
- resolve_artifact_thread
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.