Official hosted service

Give your agent QVeris tools with one URL

Connect any Streamable HTTP MCP client to the QVeris capability network. No local process, package install, or separate provider credentials.

MCP endpoint

https://mcp.qveris.ai/mcp

For OAuth, follow your client’s sign-in prompts and approve access on QVeris.

Configure your client Read the full guide

Connect ChatGPT on the web

In ChatGPT on the web, add QVeris as a custom app or connector. Availability and labels depend on your account and workspace.

Enter the MCP endpoint above and use the default OAuth settings. You do not need to open Advanced or enter a client ID or secret.
On the QVeris authorization page, choose Use account or Use API Key, then select Allow and continue. Keep the same ChatGPT account and workspace throughout.
Return to ChatGPT, select QVeris, and verify with discover and a read-only call. If the connection fails, try reconnecting.

Use API Key is an OAuth authorization option on the QVeris page. Do not paste your key into chat; the Bearer configuration below is for other clients that support it.

Read the ChatGPT connection guide

Built for dependable agent access

Zero-install transport

Use one HTTPS endpoint from any client that supports Streamable HTTP MCP.

The QVeris tool loop

Discover, inspect, and call capabilities through the same three stable MCP tools.

Credential isolation

Sessions are bound to the credential used at initialization. Start a new session when changing credentials.

Connect in three steps

Choose sign-in or an existing key

Use browser sign-in in clients with OAuth discovery. Otherwise, use an existing API key or create one in Dashboard / API Keys.

Add the remote server

Add the endpoint in your client. Complete browser sign-in, or configure the Bearer key privately if you chose the key fallback.

Verify the tools

Return to your client, run discover, and try a read-only call.

Client configuration

For other clients, use the endpoint-only configuration with OAuth discovery. Clients without OAuth can use the API-key Bearer configuration; VS Code uses a servers wrapper instead of mcpServers.

For clients with MCP OAuth discovery, copy the endpoint configuration and complete browser sign-in in your client. If your client cannot sign in, use the API key or local fallback.

Add to Cursor

Install the endpoint, then complete browser sign-in when your client asks. No API key is included.

Add to VS Code

Install the endpoint, then complete browser sign-in when your client asks. No API key is included.

Remote MCP configuration

{
  "mcpServers": {
    "qveris": {
      "type": "http",
      "url": "https://mcp.qveris.ai/mcp"
    }
  }
}

Claude Code

claude mcp add --transport http qveris https://mcp.qveris.ai/mcp --scope user

What to expect

An OAuth-capable client can use the authentication challenge to start browser sign-in. With an explicit key, 401 means the key is invalid or expired; 503 means validation is temporarily unavailable. Start a new session after changing credentials.

Need an offline local process instead? The open-source stdio package remains available in the MCP Server guide.