PeoplePerHour by Cotlet vs Trackly CLI
PeoplePerHour by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Trackly CLI is an MCP server published by kevinastuhuaman. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  PeoplePerHour by Cotlet |   Trackly CLI |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed, marked deprecated Version: 0.1.10 Downloads/month (npm): 1 767 Downloads/week (npm): 130 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.22.2 Downloads/month (npm): 1 767 Downloads/week (npm): 130 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | PeoplePerHour by Cotlet | Trackly CLI |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 3 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-24 (worse) | 2026-10-24 (better) |
| Where it runs (differs) | Remote server (cotlet.dev/mcp/v1/peopleperhour/connect) | Remote server or your machine |
| Transport (differs) | Streamable HTTP | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/cotletdev/peopleperhour-api-mcp-server | github.com/kevinastuhuaman/trackly-cli |
| Changes in the last 7 days (differs) | 6 | 10 |
| First seen (differs) | 2026-10-23 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
PeoplePerHour by Cotlet
Search projects, freelancers and Offers on PeoplePerHour, read briefs and profiles.
Trackly CLI
Job tracking CLI + MCP server for AI agents. 99K+ jobs, 775+ companies.
How to run each
PeoplePerHour by Cotlet As a remote MCP server
claude mcp add --transport http peopleperhour https://cotlet.dev/mcp/v1/peopleperhour/connectTrackly CLI As a local MCP server: npm package
claude mcp add --transport stdio trackly -- npx -y trackly-cli mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Trackly CLI has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: PeoplePerHour by Cotlet · What it can do: Trackly CLI · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.