Bisque Presentations
MCP server by Bisque · mcp
Bisque publishes narrated presentations from an agent and reads any shared one back as text. To publish: call get_presentation_spec, write one html-presentation/v1 document that follows it, call create_presentation, then poll get_presentation_status until ready is true; the result carries the watch URL. To read a presentation someone shared, call get_presentation_context with its watch URL; public and unlisted ones need no credential. To change one you can republish, call get_presentation_source, edit the HTML it returns, and send it back to create_presentation with the same presentationId, slug and visibility. To publish an HTML page or a Markdown document instead, call create_artifact with the whole document; it returns the URL once the page is live, private to the caller until share_artifact opens it up. tools/list, resources/read and prompts/get answer without a credential; tools/call needs a Bisque API key or an OAuth 2.1 token (see https://bisque.today/auth.md). Questions about…
Endpoint: https://bisque.cloud/presentations/mcp
Verification: observed. Source: crawl.
Capabilities (29)
- get_presentation_spec
- create_presentation
- publish_narrated_presentation
- get_presentation_status
- list_presentations
- get_presentation_analytics
- get_presentation_context
- get_presentation_source
- update_channel
- create_artifact
- list_artifacts
- get_artifact
- update_artifact
- share_artifact
- delete_artifact
- read_board
- edit_board
- read_artifact_analytics
- read_artifact_results
- pin_artifact
- unpin_artifact
- list_artifact_threads
- get_artifact_thread
- create_artifact_thread
- reply_to_artifact_thread