Setup
Last updated
Connect your AI assistant to the Viio MCP Server to enable SaaS portfolio analysis.
Prerequisites
- A Viio account
- For OAuth setup: An MCP client that supports OAuth with Client ID Metadata Documents (CIMD)
- For API key setup: An API key from the Viio dashboard
Authorization header.Client Compatibility
| Client | OAuth with CIMD | Notes |
|---|---|---|
| Claude.ai | Supported | Configure a custom connector. |
| Claude Desktop | Supported | Uses the same connector flow as Claude.ai. |
| Claude Code | Supported | Connect from the command line. |
| ChatGPT web | Supported | Configure a custom plugin. |
| ChatGPT desktop and Codex | Not supported | These clients currently use DCR. Use an API key if custom headers are supported. |
| Visual Studio Code | Supported | Connect with OAuth using the Viio MCP Server URL. |
| Zed | Supported | Connect with OAuth using the Viio MCP Server URL. |
Claude.ai and Claude Desktop
- Open Claude and select Customize in the sidebar.
- Select Connectors.
- Click Add, then select Add custom connector.
- Enter the following:
- Name:
Viio MCP - URL:
https://mcp.viio.io/
- Name:
- Leave the optional OAuth client ID and client secret fields empty, then click Add.
- Open the new connector and click Connect.
- Sign in to the Viio identity server with your Google or Microsoft account.
- Review the requested permissions and click Allow and continue.
- Claude returns to the connector page with the connector approved and connected.
ChatGPT Web
- Open ChatGPT in your browser and select Plugins in the sidebar.
- Click the + button on the Plugins page.
- Enter the following:
- Name:
Viio MCP - Connection:
Server URL - Server URL:
https://mcp.viio.io/ - Authentication:
OAuth
- Name:
- Check I understand and want to continue.
- Click Create.
- In the confirmation dialog, click Sign in with Viio MCP.
- Sign in to the Viio identity server with your Google or Microsoft account.
- Review the requested permissions and click Allow and continue.
- ChatGPT returns to the plugin page with the plugin connected.
Claude Code
Claude Code supports both OAuth and API key authentication.
OAuth (recommended)
claude mcp add viio --transport http https://mcp.viio.io/
Claude Code will open a browser window for you to sign in with your Viio account.
API Key Fallback
If your MCP client does not support OAuth with CIMD, create a Viio API key and set it as the raw value of the Authorization header:
Authorization: YOUR_API_KEY
Treat the API key as a secret and configure it only in an MCP client you trust.
For Claude Code:
claude mcp add viio --transport http https://mcp.viio.io/ \
--header "Authorization: YOUR_API_KEY"
Or add it manually to your .claude/settings.json:
{
"mcpServers": {
"viio": {
"type": "streamable-http",
"url": "https://mcp.viio.io/",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
Cursor
In Cursor, go to Settings > MCP Servers and add a new server:
{
"mcpServers": {
"viio": {
"url": "https://mcp.viio.io/",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
}
}
Other Clients
Any MCP-compatible client that supports OAuth with CIMD or custom HTTP headers can connect to the Viio MCP Server. Use the following details to configure it:
- Server URL:
https://mcp.viio.io/ - Transport: Streamable HTTP
If your client supports OAuth with CIMD: Point it to the server URL and follow the browser-based sign-in and consent flow. No API key is needed.
If your client does not support CIMD: Create a Viio API key and add it as the raw value of the Authorization header:
{
"url": "https://mcp.viio.io/",
"headers": {
"Authorization": "YOUR_API_KEY"
}
}
Refer to your client's documentation for the exact configuration format and confirm that it supports custom HTTP headers.
Tool Permissions
MCP clients allow you to control how each tool is used. Most clients support three permission levels per tool:
- Always allow — The tool runs automatically without prompting
- Ask each time — You're asked for approval before each use
- Never allow — The tool is disabled entirely
All Viio MCP tools are read-only — they cannot modify any data in your workspace.
Verifying the Connection
After configuring your AI assistant, test the connection by asking:
List my most expensive applications.
The AI should call the Viio MCP Server and return data from your workspace. If you see an authentication error, verify your API key is correct (for API key clients) or try reconnecting (for OAuth clients).
Troubleshooting
- Connection fails — Check that popup blockers are not preventing the OAuth redirect. Ensure the URL is exactly
https://mcp.viio.io/. - Authentication error — Verify your Viio account is active. For API key clients, check the key has not been revoked.
- Client attempts Dynamic Client Registration — The client does not support Viio's CIMD-based OAuth flow. Configure a Viio API key in the
Authorizationheader instead. - Tools not appearing — Restart your AI client after adding the configuration. Some clients require a reload.