What is qveris-agent-toolkit?

QVeris Agent Toolkit is the open-source client layer for the QVeris capability routing network, giving agents access to 10,000+ real-world capabilities across 15+ categories. It ships a CLI, MCP server, Python SDK, and REST API docs so agents can discover, inspect, invoke, and audit tools through a single protocol. Available for Cursor, Claude Code, OpenCode, and OpenClaw-style skill agents.

Is qveris-agent-toolkit open source?

Please check the official repository for license details.

qveris-agent-toolkit: QVeris Agent Toolkit is the open-source client layer for the QVeris… (★ 247)

Features

01Access 10,000+ capabilities across 15+ categories via a single protocol

02CLI, MCP server, Python SDK, and REST API in one toolkit

03Discover is free; Call returns structured pre-settlement billing

04Works with Cursor, Claude Code, and OpenClaw skill agents

05Usage audit and credits ledger for tracking tool invocations

Why choose it

+Access 10,000+ capabilities across 15+ categories via a single protocol

+Agents discovering and invoking real-world APIs without per-integration setup

+Covers 3 supported environments or platforms, which is helpful for broader deployment needs.

+The latest recorded update is 2026-07-20, which suggests the project is still actively maintained.

Trade-offs

!There are at least 8 related tools in the same category, so the best choice is easier to make after side-by-side comparison.

Compatibility

Claude Code

Native

Verified via docs

Cursor

Supported

Verified via docs

OpenClaw

Supported

Verified via docs

Quick start

$ npm install -g @qverisai/mcp

Use cases

↳Agents discovering and invoking real-world APIs without per-integration setup

↳Building MCP-based agent pipelines with pre-built capability connectors

↳Auditing and billing for tool usage in multi-agent workflows

How it compares

≈qveris-agent-toolkit sits in the Dev Tooling category, so it makes more sense to evaluate it alongside tools like fastmcp instead of in isolation.

≈If your main need is closer to "Agents discovering and invoking real-world APIs without per-integration setup", that use case is a better lens for comparison than broad feature checklists alone.

≈qveris-agent-toolkit's licensing and community traction are both easier to judge in category context.