Package Registry MCP vs StackQL MCP Server
A side-by-side look at the Package Registry MCP and StackQL MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Package Registry MCP for databases work as a local process; choose StackQL MCP Server 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 Package Registry MCP when
- You need dedicated capabilities in the Databases domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get-cargo-package-details, search-cargo-packages, list-cargo-package-versions.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 64/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39 | 1,067 |
| Directory activity | 4 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 16 | 15 |
| Full listing | View Package Registry MCP | View StackQL MCP Server |
Tools & capabilities
Package Registry MCP tools 16
get-cargo-package-detailsGet detailed information about a specific Cargo packagesearch-cargo-packagesSearch the Cargo registry for packageslist-cargo-package-versionsList all versions of a specific Cargo packageget-github-advisoryGet detailed information about a specific GitHub Security Advisory by its GHSA ID (e.g., GHSA-grv7-fg5c-xmjg).search-github-advisoriesSearch the GitHub Security Advisory Database for vulnerabilities. Filter by ecosystem (npm, pip, maven, etc.), severity, type, or CVE ID.get-package-advisoriesGet all security advisories affecting a specific package. Use this to check if a package like "braces" or "lodash" has known vulnerabilities.get-golang-package-detailsGet detailed information about a specific Go module/packagelist-golang-package-versionsList all versions of a specific Go module/packageget-npm-package-detailsGet detailed information about a specific NPM packagesearch-npm-packagesSearch the NPM registry for packageslist-npm-package-versionsList all versions of a specific NPM packageget-nuget-package-detailsGet detailed information about a specific NuGet package- +4 more on the listing page
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.reload_credentialsLive-reload provider credentials: re-sources the server's configured env file into the process environment, invalidates cached auth contexts, and reports resolution status for every installed provider (optional provider arg filters the report; changed field flags values that differ from before). Never returns secret values. Credentials resolve automatically at query time - never call this at session start or before queries. Call only after a query fails with a credential resolution error (fix the env file first, then reload, then retry) or when the user says credentials have been rotated or changed. If the report shows changed: false after a failure, the file was not updated - ask the user rather than retrying.run_lifecycle_operationExecute a stackql EXEC lifecycle operation (eg EXEC aws.ec2.instances.start_instances ...). Real cloud side effects. Discover available operations and required params via list_methods and describe_method. Returns {messages, timestamp}. Gated by server mode.run_mutation_queryExecute INSERT/UPDATE/REPLACE/DELETE against the provider. Real side effects. Returns {messages, timestamp}. Gated by server mode. Consult query_library_search for a vetted template before composing SQL from scratch; when the SQL came from a library entry, pass its id as source.- +3 more on the listing page
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.
Package Registry MCP
{
"mcpServers": {
"artmann-package-registry-mcp": {
"command": "npx",
"args": [
"-y",
"package-registry-mcp"
]
}
}
}
StackQL MCP Server
{
"mcpServers": {
"stackql-mcp-server": {
"command": "npx",
"args": [
"-y",
"@stackql/mcp-server"
]
}
}
}
Frequently asked questions
Package Registry MCP is categorized under Databases and uses a local stdio subprocess. StackQL MCP Server belongs to Databases and uses a local stdio subprocess. Pick Package Registry MCP for databases work and StackQL MCP Server 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.
Package Registry MCP is listed as free. Auth: no auth required. StackQL MCP Server is listed as free. 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 artmann-package-registry-mcp and stackql-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Package Registry MCP has a quality signal of 64/100 (Good) with 4 views, 0 installs and 39 GitHub stars. StackQL MCP Server has 71/100 (Great) with 5 views, 0 installs and 1,067 GitHub stars.