StackQL MCP Server vs Veris
A side-by-side look at the StackQL MCP Server and Veris MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose StackQL MCP Server for databases work as a local process; choose Veris for databases as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose StackQL MCP Server when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- You want tools like
describe_method, list_methods, list_providers.
Choose Veris when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 69/100 · Great | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
Tools & capabilities
StackQL MCP Server tools 15
describe_methodFull I/O contract for one method: every input with its param_type (input_required params become exact-match WHERE predicates; input_optional ones may be added) and every output field, which are the columns a SELECT or RETURNING can reference. Call it after list_methods and before the first query against a method; there is no resource-level equivalent because each method returns its own shape. Requires provider, service, resource, method.list_methodsAccess methods (HTTP operations) for a resource with their SQL verb and required params. Pick the method whose verb matches the intent and whose required params you can supply, then describe_method it. Call when composing SQL from scratch against an unfamiliar resource; not needed when executing a vetted query library template. Requires provider, service, resource.list_providersAvailable cloud/SaaS providers (top of the hierarchy). No inputs.list_registryProviders (and their versions) available in the configured registry. Distinct from list_providers, which lists only providers already pulled. Optional provider arg lists versions for that provider.list_resourcesResources under a provider.service. Requires provider and service.list_servicesServices under a provider. Requires provider.pull_providerInstall a single provider from the registry into the local approot cache. Requires provider; version is optional (latest published is pulled when empty). Writes only local cache state; no cloud control/data plane effect.query_library_getRetrieve a query library entry by id. Without params: returns the raw template, param declarations and notes (adapt from it when no exact match exists). With params: the server validates values and returns rendered SQL plus which tool to execute it with (run_select_query or run_mutation_query). Read-only, no credentials.query_library_searchSearch the curated StackQL query library by natural-language intent. Returns ranked template ids. Consult before composing SQL from scratch; follow with query_library_get, which validates params and surfaces any the index omits. Read-only, no credentials.
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.
StackQL MCP Server
{
"mcpServers": {
"stackql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}
Veris
{
"mcpServers": {
"vighriday-veris": {
"command": "npx",
"args": [
"-y",
"veris-core"
]
}
}
}
Frequently asked questions
StackQL MCP Server is categorized under Databases and uses a local stdio subprocess. Veris belongs to Databases and uses a local stdio subprocess. Pick StackQL MCP Server for databases work and Veris for databases.
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.
StackQL MCP Server has no declared pricing — check the project's own site. Veris has no declared pricing — check the project's own site. 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 stackql-mcp-server and vighriday-veris as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, StackQL MCP Server has a quality signal of 69/100 (Great) with 2 views, 0 installs and 1,067 GitHub stars. Veris has 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars.