Connect Habitify to Other MCP Clients

Our MCP server is compatible with any client that supports the Model Context Protocol. If your AI tool supports MCP, you can connect it to Habitify.

Prerequisites

An MCP-compatible AI client
A Habitify account

Server Details

Field	Value
Server URL	`https://mcp.habitify.me/mcp`
Transport	HTTP Streamable
Authentication	OAuth 2.0 (dynamic client registration)

Authentication

Our MCP server uses OAuth 2.0 with dynamic client registration. Any MCP-compatible client can register automatically — no API key is required. When you connect for the first time, you'll be prompted to sign in to your Habitify account and authorize access.

Generic Configuration

Most MCP clients accept a JSON configuration. Use the following as a template:

{
  "mcpServers": {
    "habitify": {
      "url": "https://mcp.habitify.me/mcp"
    }
  }
}

Available Tools

Once connected, the MCP server exposes these tools:

Tool	Capability
`list-habits-by-date`	List habits scheduled for a date with their status, progress, and streak information
`add-habit-log`	Record a measured value for a habit
`remove-habit-log`	Remove a habit's logs and reset its progress for a date
`complete-habit`, `fail-habit`, `skip-habit`	Update one habit's status for a date
`complete-habits`, `fail-habits`, `skip-habits`	Update selected habits in one request
`complete-all-habits`, `fail-all-habits`, `skip-all-habits`	Update all habits for a date

Creating, editing, archiving, or deleting habits and managing notes, areas, or standalone statistics are not currently exposed as MCP tools.

Rate Limits

Our MCP server shares the same rate limits as our REST API: 500 requests per minute per account. If you exceed this limit, requests will return an error until the rate limit window resets.

Troubleshooting

Connection refused

Verify the server URL is exactly https://mcp.habitify.me/mcp
Check your network connection and firewall settings

Authorization issues

Make sure you completed the sign-in and authorization step when first connecting
Try disconnecting and reconnecting to trigger a new OAuth flow

Tools not working as expected

Check our API reference for details on each endpoint's behavior
Ensure you are passing valid parameters (e.g., dates in YYYY-MM-DD format)

Prerequisites​

Server Details​

Authentication​

Generic Configuration​

Available Tools​

Rate Limits​

Troubleshooting​

Connection refused​

Authorization issues​

Tools not working as expected​

Need Help?​