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