# Wakelog [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://wakelog.wakelog.workers.dev/docs  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wakelog

## Description
Free 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.

## Tools
Capabilities this server exposes over MCP:

- **signup** — Create 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_projects** — List the changelog projects owned by the authenticated account. Requires auth.
- **create_project** — Create 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_post** — Publish 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_posts** — List the published entries of any public Wakelog project (newest first, up to 50). No auth needed.
- **lint_changelog** — Grade 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.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "wakelog": {
    "url": "https://wakelog.wakelog.workers.dev/mcp"
  }
}
```

## Documentation

## What Wakelog MCP server does

The Wakelog MCP server gives an AI agent access to a hosted changelog system through MCP. Wakelog is described as an API-first service, so the server provides an agent-facing way to work with changelog data rather than requiring the agent to call the service directly.

The available workflow covers account creation and changelog entry management. An agent can use the signup tool to create an account, then create new entries, list existing entries, and lint entries. The supplied description states that signup does not require an email address or CAPTCHA.

This server fits workflows where changelog content is created or checked as part of an agent conversation. It may also be useful when an agent needs to inspect existing entries before adding another one.

## How it works

Wakelog exposes a remote MCP endpoint at `https://wakelog.wakelog.workers.dev/mcp`. An MCP-compatible client connects to that hosted address and makes the server’s tools available to an agent. The service handles the hosted changelog side; the provided material does not describe a local process, local database, or repository checkout.

The basic interaction is tool-driven. Signup handles account creation, while the changelog tools cover writing, reading, and checking entries. Listing can provide existing changelog content to the agent, creation can add content, and linting can check an entry before it is used. Specific tool parameters and response formats are not provided in the available documentation.

## Setup and configuration

Use the hosted MCP URL as the connection target:

`https://wakelog.wakelog.workers.dev/mcp`

No environment variables or local installation steps are specified in the supplied material. Account creation is available through the signup tool, and that process is described as requiring neither email nor CAPTCHA. Client-specific connection instructions are not included, so configuration details depend on the MCP client being used.

## Tools and capabilities

The Wakelog MCP server supports these documented capabilities:

- Sign up for a Wakelog account.
- Create changelog entries.
- List changelog entries.
- Lint changelog entries.

The available description does not identify additional tools, publishing destinations, repository integrations, authentication options beyond signup, or formatting controls. Treat the four capabilities above as the supported scope unless the live documentation provides more detail.

## Limitations and notes

The provided material does not include a README, tool schemas, request examples, response examples, rate limits, account persistence details, or error behavior. It also does not name supported MCP clients. As a result, developers should verify client connection syntax and inspect the live Wakelog documentation before building a production workflow.

The Wakelog MCP server is specifically described around changelog accounts and entries. Nothing in the supplied information confirms support for issue tracking, source-control operations, deployment automation, notifications, or other developer-service functions. Its documented value is the ability to create an account and manage changelog entries through a remote MCP connection.

_Full upstream README: https://allmcps.com/mcp/wakelog/readme_