Cursor and VS Code connect to Bisque over MCP rather than installing the skills. Ask either editor for a presentation and you get back the same watch URL. Bisque narrates on its side, so there is no speech model to download.
Connect
One click adds the server to your editor:
Each adds a server called bisque pointing at
https://bisque.cloud/presentations/mcp. The editor walks you through sign-in
the first time you use it: the server asks for it, you approve in a browser,
and the editor holds the connection from then on.
Any other MCP client takes the same URL over streamable HTTP.
https://bisque.today/mcp is the same server. It is listed in the MCP
registry as cloud.bisque/presentations and today.bisque/presentations.
What to ask for
Point at something in your editor and say who is watching.
Make a two-minute presentation of this pull request for the reviewers.
Present the architecture in this folder for a new engineer.
What does https://bisque.today/p/nick/q3-review say about the budget?
The agent reads the material, writes the slides and the script, publishes, and hands you the link once the narration has finished. Ask again with a change and it republishes at the same URL.
What the connection can do
Make a presentation, check whether it has finished, list the ones you have published, see how many people watched one, and read any shared presentation back as text. The full list of tools, and how to add the server by hand, is on the MCP page.
What differs from the skills
With the skills, your machine narrates. Over MCP, Bisque does, so the first
publish involves no download and the presentation can't be rendered to an MP4
from the editor; the video skill does that, on a Mac.
Where it fits
For what to ask for and how to change a presentation, see present. This page is only about reaching the same thing from an editor.