CellarTracker vs Metorial
A side-by-side look at the CellarTracker and Metorial MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose CellarTracker for other tools and integrations work as a local process; choose Metorial for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose CellarTracker when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CT_USERNAME, CT_PASSWORD.
Choose Metorial when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
METORIAL_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Other Tools and Integrations |
| Quality signal | 43/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | CT_USERNAMECT_PASSWORD | METORIAL_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 7 | 3,366 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View CellarTracker | View Metorial |
Tools & capabilities
CellarTracker tools
No tool names declared yet. Check the project README from the listing page.
Metorial 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.
CellarTracker
{
"mcpServers": {
"cellartracker": {
"command": "npx",
"args": [
"-y",
"local-resolution"
],
"env": {
"CT_USERNAME": "YOUR_CT_USERNAME_HERE",
"CT_PASSWORD": "YOUR_CT_PASSWORD_HERE"
}
}
}
}
Metorial
{
"mcpServers": {
"metorial-metorial": {
"command": "uvx",
"args": [
"metorial"
],
"env": {
"METORIAL_API_KEY": "YOUR_METORIAL_API_KEY_HERE"
}
}
}
}
Frequently asked questions
CellarTracker is categorized under Other Tools and Integrations and uses a local stdio subprocess. Metorial belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick CellarTracker for other tools and integrations work and Metorial for other tools and integrations.
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.
CellarTracker has no declared pricing — check the project's own site. Metorial is listed as free. 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 cellartracker and metorial-metorial as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, CellarTracker has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 7 GitHub stars. Metorial has 51/100 (Good) with 1 views, 0 installs and 3,366 GitHub stars.