Claude Desktop (macOS / Windows)

OAuth (recommended):

1. Open Settings → Developer → MCP Servers → Add
2. Choose Custom HTTP MCP server
3. URL: https://mcp.varibly.com
4. Leave headers blank → Save
5. A browser window opens → click Authorize on our consent screen → done

Or with an API key: open ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and merge:

{
  "mcpServers": {
    "varibly": {
      "url": "https://mcp.varibly.com",
      "headers": {
        "Authorization": "Bearer vb_live_..."
      }
    }
  }
}

Claude Code (CLI)

OAuth:

claude mcp add --transport http varibly https://mcp.varibly.com

The first tool call opens a browser for OAuth approval.

Or with an API key:

claude mcp add --transport http varibly https://mcp.varibly.com \
  --header "Authorization: Bearer vb_live_..."

Claude.ai web

1. Settings → Connectors (or Integrations)
2. Click Add custom connector
3. Name: Varibly
4. URL: https://mcp.varibly.com
5. OAuth: leave the Authorization field blank → Claude will auto-discover OAuth and walk you through the consent flow
6. API key: add an Authorization header with value Bearer vb_live_...
7. Save → open a new chat → tools appear under the varibly namespace

Cursor

Cursor's MCP support landed in 2025 and works the same way as Claude Desktop's.

1. Open Cursor → Settings → MCP → Add new MCP server
2. Set Type: Streamable HTTP (or "remote MCP")
3. Set URL: https://mcp.varibly.com
4. OAuth: leave headers blank → first tool call opens browser → authorize
5. API key: add header Authorization: Bearer vb_live_...

Or edit ~/.cursor/mcp_config.json directly:

{
  "mcpServers": {
    "varibly": {
      "url": "https://mcp.varibly.com"
    }
  }
}

Cline (VS Code extension)

1. Open Cline's settings panel
2. Click MCP Servers → Add new server
3. Type: http (Streamable HTTP), URL: https://mcp.varibly.com
4. For OAuth: leave blank. For API key: add header Authorization: Bearer vb_live_...

Or edit Cline's config file (location depends on platform):

{
  "mcpServers": {
    "varibly": {
      "type": "http",
      "url": "https://mcp.varibly.com"
    }
  }
}

Continue.dev

Continue's MCP support is configured via .continue/config.json in your project or home directory:

{
  "mcpServers": [
    {
      "name": "varibly",
      "transport": {
        "type": "http",
        "url": "https://mcp.varibly.com"
      }
    }
  ]
}

For an API key, add a headers entry with Authorization: Bearer vb_live_....

Custom agents (TypeScript / Python / Go)

Built with the official @modelcontextprotocol/sdk:

import { Client } from '@modelcontextprotocol/sdk/client';
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp';

const client = new Client({ name: 'my-agent', version: '1.0.0' });

const transport = new StreamableHTTPClientTransport(
  new URL('https://mcp.varibly.com'),
  {
    requestInit: {
      headers: { Authorization: 'Bearer vb_live_...' }, // for API-key auth
    },
  }
);

await client.connect(transport);
const tools = await client.listTools();
const result = await client.callTool({ name: 'varibly_compile_blueprint', arguments: { ... } });

For OAuth in custom agents, use the SDK's OAuthClientProvider to drive the auth code + PKCE flow against our endpoints. Discovery starts at https://api.varibly.com/oauth/.well-known/openid-configuration.

Other / generic MCP client

Any client that implements the MCP Streamable HTTP transport will work. Provide:

• Endpoint: https://mcp.varibly.com
• Transport: Streamable HTTP (per the March-2025 MCP spec; SSE-only is deprecated)
• Auth: Bearer token in the Authorization header (either an OAuth access token or a vb_live_* API key)

If your client supports OAuth 2.1 with Dynamic Client Registration, send a request without auth — our 401 + WWW-Authenticate header tells your client where to find the auth server, and your client should auto-register and complete the flow.