MCP Server

The MCP (Model Context Protocol) Server allows you to operate Manako monitoring directly from AI agents like Claude Desktop or Claude Code.

Setup

Claude Code

Add the following to your project’s .mcp.json:

{
  "mcpServers": {
    "manako": {
      "type": "http",
      "url": "https://mcp.manako.dev/mcp"
    }
  }
}

Restart Claude Code, and the Manako tools will become available.

Claude Desktop

Add the same configuration to your settings file (claude_desktop_config.json).

Authentication

The MCP Server supports two authentication methods.

Browser Authentication (Recommended)
API Key Authentication

No pre-configured API key is required. Ask Claude to “Log in to Manako,” and the auth tool will return a browser verification URL and code. Approve the code in your browser, then the auth_status tool will establish the session.

Sessions are valid for 24 hours. Please log in again when the session expires.

Set the API key via environment variables:

{
  "mcpServers": {
    "manako": {
      "type": "http",
      "url": "https://mcp.manako.dev/mcp",
      "headers": {
        "Authorization": "Bearer ${MANAKO_API_KEY}"
      }
    }
  }
}

export MANAKO_API_KEY=mk_your_api_key_here

Available Tools

auth

Start browser-based authentication. Returns a verification URL and code to approve in your browser.

auth()

auth_status

Check the status of a pending browser authentication. Once approved, the session is established automatically.

auth_status(deviceCode)

monitors

Manage monitors.

Action	Description	Required Parameters
`list`	List all monitors	-
`get`	Get monitor details	`id`
`create`	Create a monitor	`name`, `url` or `config`
`update`	Update a monitor	`id`
`delete`	Delete a monitor	`id`

Creation Parameters

Parameter	Description
`name`	Monitor name
`type`	Type (http, tcp, ping, heartbeat, webchange, ssl, domain)
`url`	URL (shortcut for HTTP type)
`config`	Type-specific configuration object
`intervalSeconds`	Check interval (300-86400 seconds)

Update Parameters

Parameter	Description
`id`	Monitor ID
`name`	New name
`isActive`	Enable/disable toggle
`intervalSeconds`	New check interval

incidents

Manage incidents.

Action	Description	Required Parameters
`list`	List incidents	-
`acknowledge`	Mark as acknowledged	`id`
`create`	Create manual incident	`title`
`update`	Update incident	`id` + `title` or `cause`
`resolve`	Resolve incident	`id`
`delete`	Delete manual incident	`id`

Use the status parameter with list to filter results (ongoing, resolved, acknowledged). create accepts an optional cause (description). You can also add a resolution note via cause when using resolve.

status-pages

Manage status pages.

Action	Description	Required Parameters
`list`	List all status pages	-
`stats-reset`	Reset monitor statistics	`id`

notification-channels

Test notification channels.

Action	Description	Required Parameters
`test`	Send test notification	`id`

webhook-subscriptions

Manage event webhook subscriptions.

Action	Description	Required Parameters
`list`	List subscriptions	-
`create`	Create subscription	`targetUrl`, `secret`, `events`
`delete`	Delete subscription	`id`

Supported events: incident.created, incident.resolved, webchange.detected

audit-logs

View audit logs (paid plan only).

Action	Description	Required Parameters
`list`	List audit logs	-

Filter with actionFilter, resourceType, userId, from, to, limit.

Common Options

Specify verbose: true on any tool to get the complete JSON data from the API response.

Usage Examples

You can ask the AI agent things like:

“Log in to Manako”
“Show me the list of monitors”
“Create an HTTP monitor for example.com”
“Are there any ongoing incidents?”
“Pause monitor XXX”