Skip to main content
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.
Some organisations block adding custom connectors or plugins. Visk will be published as an official connector soon — in the meantime, try accessing the Visk MCP through a coding agent such as Claude Code if that’s available to you.
Some clients sandbox network access and block the upload. In Claude.ai, go to Settings → Capabilities and set Domain allowlist to All domains. If that’s not an option, upload your .pptx directly at visk.com/themes and ask your agent to use it.
Corruptions are rare but can happen in edge cases. PowerPoint’s built-in auto-repair usually fixes the file so you can keep working with it. If you’re happy to share, email the corrupted deck to support@visk.com so we can track down the cause. If it keeps happening, the slide master is the likely culprit — try starting from a blank master instead.
You can see a full history of your usage and credit consumption in the Usage tab at visk.com/settings. If anything looks off, email support@visk.com and we’ll investigate.
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…”.
Still stuck? Reach us at support@visk.com.