delete_artifact — Bisque Presentations MCP Tool Mutating
delete_artifact
(delete artifact) 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 delete_artifact from your client
- Claude Code Bisque Presentations delete_artifact run in your project directory
- Claude Desktop Bisque Presentations delete_artifact ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Bisque Presentations delete_artifact ~/.cursor/mcp.json
- VS Code Bisque Presentations delete_artifact .vscode/mcp.json
- Zed Bisque Presentations delete_artifact ~/.config/zed/settings.json
- Windsurf Bisque Presentations delete_artifact ~/.codeium/windsurf/mcp_config.json
- Cline Bisque Presentations delete_artifact ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Bisque Presentations delete_artifact ~/.gemini/settings.json
- Grok Bisque Presentations delete_artifact .mcp.json (in your project root)
- ChatGPT Bisque Presentations delete_artifact Settings → Connectors → Advanced → Developer mode
- Claude.ai Bisque Presentations delete_artifact Settings → Connectors → Add custom connector
- LangChain Bisque Presentations delete_artifact 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
- update_channel
- create_artifact
- list_artifacts
- get_artifact
- update_artifact
- share_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.