Portfolio MCP Server vs Wakelog — MCP Server Comparison | AllMCPs
Portfolio MCP Server vs Wakelog
A side-by-side look at the Portfolio MCP Server and Wakelog MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Portfolio MCP Server 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?
Choose Portfolio MCP Server when
You need dedicated capabilities in the Developer Tools domain.
You prefer a local stdio subprocess transport.
You want tools like list_projects, get_flagship_project, get_resume_summary.
get_flagship_projectThe single best project to look at first
get_resume_summaryBackground, target role, and core stack
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.
lint_changelogGrade a CHANGELOG.md against 12 best-practice checks (dates, ordering, vague titles, commit dumps, unflagged breaking changes...). Returns a grade A-F, score /100 and specific findings. No auth needed. Max 30 runs/hour.
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.
Portfolio MCP Server is categorized under Developer Tools and uses a local stdio subprocess. Wakelog belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Portfolio MCP Server 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.
Portfolio MCP Server has no declared pricing — check the project's own site. 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 portfolio-mcp-server and wakelog as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Portfolio MCP Server has a quality signal of 51/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Wakelog has 68/100 (Great) with 1 views, 0 installs and 0 GitHub stars.