QVeris Agent Toolkit vs One
A side-by-side look at the QVeris Agent Toolkit and One MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose QVeris Agent Toolkit for aggregators work over a hosted endpoint; choose One for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose QVeris Agent Toolkit when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
QVERIS_API_KEY.
Choose One when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ONE_SECRET. - You want tools like
list_one_integrations, find_one_actions, execute_one_action.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 61/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | API key required |
| Pricing | Freemium | Not declared |
| Required env vars | QVERIS_API_KEY | ONE_SECRET |
| Verified owner | Community listing | Community listing |
| GitHub stars | 263 | 11 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View QVeris Agent Toolkit | View One |
Tools & capabilities
QVeris Agent Toolkit tools
No tool names declared yet. Check the project README from the listing page.
One tools 3
list_one_integrationsList the platforms the user has connected on One. ALWAYS call this tool first in any workflow. Each connection has the kebab-case `platform` name (e.g., 'ship-station', 'shopify') and the `key` (the connectionKey for execute_one_action) you'll need for subsequent tool calls. Each connection carries an `access` field describing what you may run on it: `full`, a set of allowed HTTP `methods`, or a specific list of `actions` (each with `actionId`, `title`, `method`). When a connection is action-scoped, its `actions` are exactly what may run, so you need not search.find_one_actionsUse this to find the API actions a task needs, on any platforms, in one call: send one `requests` entry per operation (platform and a short intent) and get back, for each, the action to use with its documentation, plus a few alternatives. Large documents come back as a digest; call again with `load` for a section it omitted, the whole document, the table of contents, or an alternative's documentation. Results are limited to what this server's settings allow. Call list_one_integrations first to see the connected platforms.execute_one_actionExecute a One action to perform actual operations on third-party platforms. CRITICAL: Only call this when the user's intent is to EXECUTE an action (e.g., 'read my last Gmail email', 'fetch 5 contacts from HubSpot', 'create a task in Asana'). DO NOT call this when the user wants to BUILD or CREATE code/forms/applications - in those cases, stop after find_one_actions and provide implementation guidance instead. REQUIRED WORKFLOW: Must call find_one_actions first, which returns the action's documentation. If uncertain about execution intent or parameters, ask for confirmation before proceeding.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
QVeris Agent Toolkit
{
"mcpServers": {
"mcp-202": {
"url": "https://img.shields.io/npm/v/@qverisai/mcp?label=mcp"
}
}
}
One
{
"mcpServers": {
"one": {
"command": "npx",
"args": [
"-y",
"@withone/mcp"
],
"env": {
"ONE_SECRET": "YOUR_ONE_SECRET_HERE"
}
}
}
}
Frequently asked questions
QVeris Agent Toolkit is categorized under Aggregators and uses a remote HTTP/SSE transport. One belongs to Aggregators and uses a local stdio subprocess. Pick QVeris Agent Toolkit for aggregators work and One for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
QVeris Agent Toolkit is listed as freemium — a free tier with paid plans. Auth: api key required. One has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-202 and one as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, QVeris Agent Toolkit has a quality signal of 61/100 (Good) with 0 views, 0 installs and 263 GitHub stars. One has 64/100 (Good) with 0 views, 0 installs and 11 GitHub stars.