Content Tools

bisque.today

Creates and publishes narrated presentations from HTML documents.

1 endpoint8 known toolsFirst detected September 1, 2026Last detected September 6, 2026

ENDPOINT 1

https://bisque.cloud/presentations/mcp

No auth detected

MCP server metadata

Name: bisque-presentations
Version: 1.0.0

Capabilities

toolspromptsresources

Server instructions

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. 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 how Bisque works go to the docs server at https://bisque.today/docs/mcp.

Known tools 8

get_presentation_spec

Fetch the html-presentation/v1 authoring contract: document structure, the dual landscape/vertical layout rule, and the narration markup that makes slides speak.

Inferred read-only

create_presentation

Generate a narrated presentation from an html-presentation/v1 document.

Inferred read-only

publish_narrated_presentation

Publish an html-presentation/v1 document using audio YOU synthesized locally (e.

Potential side effects

get_presentation_status

Fetch the build state and result URL for a presentationId.

Inferred read-only

list_presentations

List the authenticated user's presentations.

Inferred read-only

get_presentation_analytics

Watch analytics for one of your presentations: views, likes, completion rate, per-slide retention funnel, traffic sources, distinct signed-in/anonymous viewers, and organization email domains (personal providers filtered).

Potential side effects

get_presentation_context

Load any shared Bisque presentation for reading: its metadata, the full per-slide narration transcript with timestamps, and the context.

Inferred read-only

update_channel

Update one of your channels.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.bisque-presentations]
url = "https://bisque.cloud/presentations/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "bisque-presentations": {
      "type": "http",
      "url": "https://bisque.cloud/presentations/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: bisque-presentations
Remote MCP URL: https://bisque.cloud/presentations/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "bisque-presentations": {
      "url": "https://bisque.cloud/presentations/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "bisque-presentations": {
      "type": "http",
      "url": "https://bisque.cloud/presentations/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "bisque-presentations",
  "transport": "streamable-http",
  "url": "https://bisque.cloud/presentations/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.