Other clients

Cline, Continue, JetBrains, custom agents — and how to call the server directly.

The server is a standard streamable-HTTP MCP endpoint with a bearer header. Anything that speaks MCP can use it.

The two config shapes

Most clients use one of these. Try the HTTP form first:

{
  "mcpServers": {
    "vuesax": {
      "url": "https://mcp.vuesax.com",
      "headers": { "Authorization": "Bearer vsx_your_key_here" }
    }
  }
}

If the client only launches processes (stdio), bridge it:

{
  "mcpServers": {
    "vuesax": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.vuesax.com",
        "--header",
        "Authorization: Bearer vsx_your_key_here"
      ]
    }
  }
}

Cline / Roo (VS Code extensions)

Open the MCP servers panel → Configure MCP Servers → paste the HTTP form above into cline_mcp_settings.json. Restart the panel afterwards.

Continue

Add it under mcpServers in ~/.continue/config.yaml (or config.json on older versions), using the same URL and header. MCP tools are available in agent mode only.

JetBrains AI Assistant / Junie

Settings → Tools → AI Assistant → MCP → Add → choose the remote/HTTP type and paste the URL plus the Authorization header. If your build only offers a command, use the mcp-remote bridge.

Custom agents

Any MCP client library works — point it at the URL and set the header.

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

const transport = new StreamableHTTPClientTransport(
  new URL('https://mcp.vuesax.com'),
  { requestInit: { headers: { Authorization: `Bearer ${process.env.VUESAX_KEY}` } } }
);

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

const { tools } = await client.listTools();
const res = await client.callTool({
  name: 'search_components',
  arguments: { query: 'button loading' },
});

Tool names, parameters and return shapes are listed in the MCP overview.

Checking the endpoint by hand

A quick reachability test — an empty POST answers with a protocol error, not a network one, which is enough to prove the key and URL are right:

curl -i -X POST https://mcp.vuesax.com \
  -H "Authorization: Bearer $VUESAX_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

• 200 with a tool list — you’re connected.
• 401 — key missing, malformed (must start with vsx_), revoked, or not PRO.
• 503 with Retry-After — auth backend blipped; retry in a few seconds.