Koskamo

HabitLog Pro MCP

An official MCP server for HabitLog Pro that allows AI assistants to read and write a user's habit data. It supports checking in habits via natural language, managing habit schedules and aliases, retrieving streaks and date-range summaries, and handling habit creation or archiving.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

HabitLog Pro MCP logo, by HabitLog ProVendor evidenceStreamable HTTPOAuth sign-inEndpoint checked 2026-11-01Operated by HabitLog Pro
You need:Sign in with Google on the HabitLog Pro screenOAuth 2.1 with PKCELeave the OAuth fields empty
MCP endpoint (Streamable HTTP)
https://habitlogpro.com/mcp
Vendor documentation

What you can do with it

  • Check in multiple habits for a day using a single sentence
  • Retrieve daily check-ins, streaks, and date-range summaries
  • Create, update, or archive habits and their schedules
  • Resolve habit names and aliases for consistent tracking

Source and maintenance

Vendor evidenceRegistry 1.0.0

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
142 ms
95th percentile latency
142 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 142 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http habitlog-pro-mcp https://habitlogpro.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add habitlog-pro-mcp --url https://habitlogpro.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable habitlog-pro-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "habitlog-pro-mcp": {
      "url": "https://habitlogpro.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "habitlog-pro-mcp": {
      "type": "streamableHttp",
      "url": "https://habitlogpro.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start habitlog-pro-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "habitlog-pro-mcp": {
      "type": "http",
      "url": "https://habitlogpro.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http habitlog-pro-mcp https://habitlogpro.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "habitlog-pro-mcp": {
      "url": "https://habitlogpro.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "habitlog-pro-mcp": {
      "serverUrl": "https://habitlogpro.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like HabitLog Pro MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run HabitLog Pro MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing