Package Registry MCP vs FireCMS Cloud
A side-by-side look at the Package Registry MCP and FireCMS Cloud 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 FireCMS Cloud 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 FireCMS Cloud 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 | 64/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 39 | 1,281 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | Not listed |
| Full listing | View Package Registry MCP | View FireCMS Cloud |
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
FireCMS Cloud tools
No tool names declared yet. Check the project README from 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"
]
}
}
}
FireCMS Cloud
{
"mcpServers": {
"firecms-cloud": {
"command": "npx",
"args": [
"-y",
"create-firecms-app"
]
}
}
}
Frequently asked questions
Package Registry MCP is categorized under Databases and uses a local stdio subprocess. FireCMS Cloud belongs to Databases and uses a local stdio subprocess. Pick Package Registry MCP for databases work and FireCMS Cloud 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. FireCMS Cloud 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 artmann-package-registry-mcp and firecms-cloud 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. FireCMS Cloud has 52/100 (Good) with 1 views, 0 installs and 1,281 GitHub stars.