The client can't connect, or requests come back as 307 redirects
The client can't connect, or requests come back as 307 redirects
Make sure the URL ends with a trailing slash:
https://api.visk.com/mcp/. Without it the server redirects, and some MCP clients don’t follow the redirect.Requests fail with 406 Not Acceptable
Requests fail with 406 Not Acceptable
Visk uses the MCP streamable HTTP transport, which requires the header
Accept: application/json, text/event-stream. MCP clients send this automatically; if you’re calling the endpoint by hand, add it yourself. Responses come back framed as server-sent events.My client only supports local (stdio) MCP servers
My client only supports local (stdio) MCP servers
Bridge through
mcp-remote: npx -y mcp-remote https://api.visk.com/mcp/. The Other clients tab on the setup page has details.A tool call failed with session_expired (410)
A tool call failed with session_expired (410)
The workspace behind that session id is gone. Ask the AI to start a fresh session and re-upload the file — or just re-run your request; agents normally recover from this on their own.
The download link stopped working
The download link stopped working
Export links are valid for 6 hours. Ask for the deck to be exported again — the session still has the latest state, so it’s a single call.
The AI built a deck without using Visk
The AI built a deck without using Visk
Check the server is actually connected (e.g.
claude mcp list in Claude Code), then mention Visk explicitly: “use Visk to build a PowerPoint about…”. Once it has used the tools once, it picks them up naturally.