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

Get an API key Read the full 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

Each session is bound to one API key and cannot switch credentials after initialization.

Connect in three steps

Create an API key

Open Dashboard / API Keys and create a key for your agent.

Add the remote server

Use the endpoint below and send your key as a Bearer token on every request.

Verify the tools

Reconnect your client and confirm that discover, inspect, and call appear.

Client configuration

Use this JSON shape in clients that accept remote MCP server configuration. Keep the key in a secret or environment variable when your client supports it.

Replace YOUR_QVERIS_API_KEY locally. Never commit an API key to source control.

Remote MCP configuration

{
  "mcpServers": {
    "qveris": {
      "type": "http",
      "url": "https://mcp.qveris.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_QVERIS_API_KEY"
      }
    }
  }
}

Claude Code

claude mcp add --transport http qveris https://mcp.qveris.ai/mcp --scope user --header "Authorization: Bearer YOUR_QVERIS_API_KEY"

What to expect

The server validates the key when a session starts. A 401 means the key is missing or invalid; a 503 means validation is temporarily unavailable. If your key changes, start a new MCP session.

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