Time Management vs MCP For API
A side-by-side look at the Time Management and MCP For API MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
T
Time ManagementDeveloper Tools · Local subprocess (stdio)Read your Pyunto Time Management schedule and log time from an AI assistant. E2EE project planning.40FairAuth: not declaredVerdict: choose Time Management for developer tools work as a local process; choose MCP For API for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
TChoose Time Management when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PYUNTO_TM_API_KEY.
Choose MCP For API when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | T Time Management | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 40/100 · Fair | 44/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | PYUNTO_TM_API_KEY | None listed |
| Verified owner |
Tools & capabilities
Time Management tools
No tool names declared yet. Check the project README from the listing page.
MCP For API 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.
Time Management
{
"mcpServers": {
"time-management": {
"command": "npx",
"args": [
"-y",
"@pyunto/tm-mcp"
],
"env": {
"PYUNTO_TM_API_KEY": "YOUR_PYUNTO_TM_API_KEY_HERE"
}
}
}
}
MCP For API
{
"mcpServers": {
"mcp-for-api": {
"url": "https://mcp.appwrite.io/"
}
}
}
Frequently asked questions
Time Management is categorized under Developer Tools and uses a local stdio subprocess. MCP For API belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Time Management for developer tools work and MCP For API for developer tools.
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.
Time Management has no declared pricing — check the project's own site. MCP For API has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 time-management and mcp-for-api as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Time Management has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP For API has 44/100 (Fair) with 2 views, 0 installs and 72 GitHub stars.