← Back to Docs

Connecting AI Clients (MCP)

Developer

Connecting AI Clients (MCP)

Priiism exposes a network-reachable Model Context Protocol (MCP) endpoint, so you can drive your project from your own AI client. The MCP Quickstart covers the endpoint and a raw curl walkthrough; this page gives you the exact setup for specific clients and tells you which clients work today.

What every client needs

Regardless of the client, an MCP connection to Priiism is always the same three things:

SettingValue
Transportstreamable-http (some clients call it http)
URLhttps://YOUR-APP-HOST/api/mcp/v1
AuthAuthorization: Bearer vk_live_… header (create a key)

Replace YOUR-APP-HOST with your dashboard host and vk_live_… with a real key. A project-scoped key is simplest — the project is implied, so you don’t name it on every call. Give the key only the scopes the client needs.

Two ways to connect. Header-based clients — Claude Code, Cursor, and most generic MCP clients — attach a vk_ API key as a Bearer header. OAuth-based clients — Claude Desktop and ChatGPT connectors — connect by URL and sign in through a browser (no key to paste); see Claude Desktop. Both paths reach the same tools.

Claude Code

Claude Code speaks the streamable-HTTP transport and accepts custom headers, so a single command registers Priiism:

claude mcp add --transport http priiism \
  https://YOUR-APP-HOST/api/mcp/v1 \
  --header "Authorization: Bearer vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Verify the connection:

claude mcp list          # priiism should appear as connected

Then, inside Claude Code, run /mcp to inspect the server, or just ask it to use a Priiism tool (for example, “get this project’s info”). The tools your key is allowed to use are filtered by its scopes.

To remove it later: claude mcp remove priiism.

Cursor

Cursor is configured with a JSON block (Settings → MCP, or an mcp.json file). Add a streamable-http server entry pointing at the endpoint with your key as an Authorization header:

{
  "mcpServers": {
    "priiism": {
      "type": "streamable-http",
      "url": "https://YOUR-APP-HOST/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

After saving, Priiism appears in Cursor’s MCP list with its available tools. If it shows as disconnected, re-check the URL and that the Authorization value starts with Bearer .

Other MCP clients

Any client that supports the MCP streamable-HTTP transport with a custom header can connect. Field names vary — some use servers instead of mcpServers, some use transport instead of type — but the three values are always the same:

{
  "mcpServers": {
    "priiism": {
      "type": "streamable-http",
      "url": "https://YOUR-APP-HOST/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

If your client can’t attach a custom header but supports remote MCP servers by URL, use the OAuth path instead — see Claude Desktop.

Verify any connection

Independent of the client, you can confirm the endpoint and key work with curl. List the tools your key can use:

curl -X POST https://YOUR-APP-HOST/api/mcp/v1 \
  -H "Authorization: Bearer vk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A JSON-RPC result with a tools array means auth, scopes, and dispatch are all working. See the MCP Quickstart for a full tools/call example and the AI Agent Tools catalog for what you can call.

Claude Desktop

Claude Desktop connects to Priiism as a custom connector over OAuth — you give it the endpoint URL and sign in through your browser. No API key to create or paste; the connection is tied to your Priiism account. (Custom connectors require a paid Claude plan.)

  1. In Claude Desktop, open Settings → Connectors and choose Add custom connector.
  2. Name: Priiism. URL: https://YOUR-APP-HOST/api/mcp/v1. Add it.
  3. Click Connect. A browser opens to Priiism:
    • Sign in if you aren’t already.
    • On the consent screen, choose a project to bind the connection to (so tools act on it automatically), or leave it org-wide, then click Allow.
  4. Claude Desktop shows the connector as connected, with its tools available. Ask it to use one — for example, “list my Priiism projects” or “show this project’s info.”

Behind the scenes Claude discovers the authorization server, registers itself, and stores the access token; it renews access automatically, so the connection persists. To review or disconnect it later, use Settings → Connectors in Claude, or Account Settings → Developer → Connected AI clients in Priiism.

If you didn’t pick a project (org-wide), name one per request — for example, “using project abc123, list environment variables.”

ChatGPT

ChatGPT connects to remote MCP servers over the same OAuth flow, in its connector / developer-mode surface (availability and exact steps vary by ChatGPT plan and are evolving). Add a connector pointing at https://YOUR-APP-HOST/api/mcp/v1 and complete the browser sign-in and consent, exactly as for Claude Desktop above.

Which tools a connection gets

OAuth connections grant the standard (non-elevated) scopes by default, shown on the consent screen when you connect. Elevated capabilities (running arbitrary SQL, sandbox commands, code search, autonomous runs) are never granted automatically. To scope a connection tightly, use a project-scoped, minimally-scoped vk_ key with a header-based client instead (see Scopes).

Troubleshooting

  • 401 unauthorized — the Authorization header is missing, or the key is invalid, revoked, or expired. Re-check the key value and the Bearer prefix; see API Reference → Errors.
  • Tool call returns an error result — the tool isn’t permitted by your key’s scopes. Widen the key’s scopes, or (for an org-wide key) pass the target project in the tool’s arguments: { "project": "YOUR-PROJECT-ID" }.
  • A file-editing tool reports it isn’t available remotely yet — a small set of tools that read or write the sandbox working directory are listed but not yet callable over the remote transport. Everything else works today.
  • Client shows “connected” but no tools — your key may have no scopes granted; add at least one read scope. tools/list only returns tools your key can call.
  • OAuth connect (Claude Desktop / ChatGPT) opens a login loop — make sure you complete the Priiism sign-in in the browser window the client opens, then approve the consent screen. The connection is bound to that Priiism account.
  • OAuth connect says the request expired — the consent page is single-use and time-limited; if you left it open too long, start the connect again from the client.
  • To disconnect an OAuth client — remove it in the client, or revoke it from Account Settings → Developer → Connected AI clients; access stops immediately.

Next steps