Chatpack MCP vs Wakelog
A side-by-side look at the Chatpack MCP and Wakelog MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Chatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.86ExcellentAuth: no auth requiredW
WakelogDeveloper Tools · Remote HTTP/SSEFree API-first hosted changelog with a remote MCP server at https://wakelog.wakelog.workers.dev/mcp — agents can create an account (signup tool, no email/CAPTCHA) and create, list, and lint changelog entries natively.68GreatAuth: api key requiredVerdict: choose Chatpack MCP for developer tools work as a local process; choose Wakelog 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?
CChoose Chatpack MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
search_docs, get_document, get_integration_guide.
WChoose Wakelog when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
signup, list_projects, create_project.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Chatpack MCP | W Wakelog |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 86/100 · Excellent | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | API key required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified |
Tools & capabilities
Chatpack MCP tools 5
search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.
Wakelog tools 6
signupCreate a free Wakelog account (no email, no CAPTCHA — agents welcome). Returns an api_token: configure it as `Authorization: Bearer <api_token>` on this MCP server to use the authenticated tools, and STORE the one-time recovery_key. Max 5 signups/hour per network.list_projectsList the changelog projects owned by the authenticated account. Requires auth.create_projectCreate a changelog project. Its public page will be at https://wakelog.wakelog.workers.dev/p/<slug> with RSS/JSON feeds, an embeddable widget, and a README badge. Requires auth.create_postPublish a changelog entry (or save a draft / schedule it). This is the core action: what you shipped, in markdown. Requires auth. Max 60 posts/hour.list_postsList the published entries of any public Wakelog project (newest first, up to 50). No auth needed.
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.
Chatpack MCP
{
"mcpServers": {
"chatpack-mcp": {
"command": "npx",
"args": [
"-y",
"@chatpack/mcp"
]
}
}
}
Wakelog
{
"mcpServers": {
"wakelog": {
"url": "https://wakelog.wakelog.workers.dev/mcp"
}
}
}
Frequently asked questions
Chatpack MCP is categorized under Developer Tools and uses a local stdio subprocess. Wakelog belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Chatpack MCP for developer tools work and Wakelog 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.
Chatpack MCP is listed as free. Auth: no auth required. Wakelog 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 chatpack-mcp and wakelog as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chatpack MCP has a quality signal of 86/100 (Excellent) with 2 views, 0 installs and 224 GitHub stars. Wakelog has 68/100 (Great) with 1 views, 0 installs and 0 GitHub stars.