CellarTracker vs Time
A side-by-side look at the CellarTracker and Time 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 Time 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 Time when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
get_current_time, convert_time.
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 | 83/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CT_USERNAMECT_PASSWORD | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 7 | 91,540 |
| Directory activity | 0 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View CellarTracker | View Time |
Tools & capabilities
CellarTracker tools
No tool names declared yet. Check the project README from the listing page.
Time tools 2
get_current_timeGet current time in a specific timezoneconvert_timeConvert time between timezones
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"
}
}
}
}
Time
{
"mcpServers": {
"time": {
"command": "uvx",
"args": [
"mcp-server-time"
]
}
}
}
Frequently asked questions
CellarTracker is categorized under Other Tools and Integrations and uses a local stdio subprocess. Time belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick CellarTracker for other tools and integrations work and Time 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. Time is listed as free. Auth: no auth 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 time 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. Time has 83/100 (Excellent) with 5 views, 0 installs and 91,540 GitHub stars.