Client setup

Visk is a remote MCP server over streamable HTTP. Any MCP client can connect. Add the endpoint, then just ask your AI for a presentation. Sign-in happens in your client: on first connect it opens a browser window to authorise with your Visk account over OAuth. There are no API keys to create or paste, and nothing to put in a config file.

Endpoint

Paste this URL into the setup steps below. Keep the trailing slash.

Server URL

https://api.visk.com/mcp/

One-click install

Install in any of these clients with a single click.

Install in Cursor

One-click install for Cursor.

Install in VS Code

One-click install for VS Code.

Install in LM Studio

One-click install for LM Studio.

Install in Goose

One-click install for Goose.

The LM Studio and Goose links open the desktop app directly, so they only work if it’s installed. For Claude Code, Claude.ai, Codex, ChatGPT and other clients, use the steps below — those use a CLI command, a settings page, or a JSON config file rather than deep links.

Install in your client

Claude Code
Claude.ai (web)
Codex
ChatGPT

Add the server

In your terminal, run:

claude mcp add --transport http visk https://api.visk.com/mcp/

Authenticate

Open Claude Code and type /mcp, then select visk. Select Authenticate and complete the authorization.

Add the connector

Go to Settings → Connectors and select Add custom connector.

Enter the details

Enter the name Visk and the MCP server URL https://api.visk.com/mcp/, then click Add.

Authorize

Click Connect and complete the authorization.

Add the server

In your terminal, run:

codex mcp add visk --url https://api.visk.com/mcp/

Authorize

Your browser will be opened automatically for OAuth. Click Allow to complete the authorization.

Enable Developer Mode

Hover over your personal account and open Settings, then go to Plugins → Developer Mode and enable Developer Mode.

Create the plugin

Return to the main page, click Plugins in the upper-left corner, then click the + icon next to the search bar to create a new plugin.

Enter the details

Enter the plugin name visk and the connection URL https://api.visk.com/mcp/.

Connect

Click Create and connect to complete setup.

Installation reference

Cursor

Add to ~/.cursor/mcp.json, or .cursor/mcp.json for a single project:

{
  "mcpServers": {
    "visk": {
      "url": "https://api.visk.com/mcp/"
    }
  }
}

See the Cursor MCP documentation for more.

VS Code

Create .vscode/mcp.json in your workspace, or run the MCP: Open User Configuration command for a user-level file:

{
  "servers": {
    "visk": {
      "type": "http",
      "url": "https://api.visk.com/mcp/"
    }
  }
}

VS Code uses a top-level servers object rather than Cursor’s mcpServers, and needs type: "http". See the VS Code MCP documentation.

Other clients

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "visk": {
      "serverUrl": "https://api.visk.com/mcp/"
    }
  }
}

Windsurf uses serverUrl rather than url. See the Windsurf MCP documentation.

Gemini CLI

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "visk": {
      "httpUrl": "https://api.visk.com/mcp/"
    }
  }
}

See the Gemini CLI MCP documentation.

Kiro

Add to .kiro/settings/mcp.json for a workspace, or ~/.kiro/settings/mcp.json globally:

{
  "mcpServers": {
    "visk": {
      "url": "https://api.visk.com/mcp/"
    }
  }
}

See the Kiro MCP documentation.

OpenCode

Add to opencode.json in your project, or ~/.config/opencode/opencode.json globally:

{
  "mcp": {
    "visk": {
      "type": "remote",
      "url": "https://api.visk.com/mcp/",
      "enabled": true
    }
  }
}

See the OpenCode MCP documentation.

Zed, Warp, Raycast and other stdio-only clients

These clients support only stdio-transport MCP servers, so they can’t reach a remote HTTP endpoint directly. Bridge through mcp-remote, which handles the OAuth flow for you:

{
  "mcpServers": {
    "visk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.visk.com/mcp/"]
    }
  }
}

Where this goes differs per client — see the Zed, Warp or Raycast MCP docs for the exact file and wrapper format.

If your client isn’t listed, most accept the mcpServers format shown in the Cursor section. Check your client’s docs for the field names it expects — VS Code uses servers, Windsurf uses serverUrl, Gemini CLI uses httpUrl.

Best practices

Mention Visk by name at first

Once an agent has used the tools once it reaches for them naturally, but on the first request in a session it may build a deck by other means. “Use Visk to build a PowerPoint about…” is enough to anchor it.

Attach a deck to inherit its brand

Uploading an existing .pptx gives the agent your masters, layouts and theme to work from, so new slides come out on-brand without you describing the styling. It’s usually faster than prompting for colours and fonts.

Let it check its own work

Visk renders slides to PNG, and agents that screenshot as they go catch overflow and layout problems you’d otherwise find in PowerPoint. Iterating on a slide costs nothing extra, so there’s no reason to discourage it — see Pricing.

Troubleshooting

Connection not working? See troubleshooting for the handful of issues behind nearly all problems.

Getting started

MCP

Visk HTML

Help

Client setup

Endpoint

One-click install

Install in Cursor

Install in VS Code

Install in LM Studio

Install in Goose

Install in your client

Installation reference

Cursor

VS Code

Other clients

Best practices

Mention Visk by name at first

Attach a deck to inherit its brand

Let it check its own work

Troubleshooting

​Endpoint

​One-click install

Install in Cursor

Install in VS Code

Install in LM Studio

Install in Goose

​Install in your client

​Installation reference

​Cursor

​VS Code

​Other clients

​Best practices

​Mention Visk by name at first

​Attach a deck to inherit its brand

​Let it check its own work

​Troubleshooting

Endpoint

One-click install

Install in your client

Installation reference

Cursor

VS Code

Other clients

Best practices

Mention Visk by name at first

Attach a deck to inherit its brand

Let it check its own work

Troubleshooting