> For the complete documentation index, see [llms.txt](https://docs.mozilla.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozilla.ai/mcpd/cli-reference/mcpd_daemon.md).

# daemon

Launches an `mcpd` daemon instance

## Synopsis

Launches an `mcpd` daemon instance, which starts MCP servers and provides routing via HTTP API

```
mcpd daemon [--dev] [--addr] [--cors-enable] [--cors-origin]... [flags]
```

## Options

```
      --addr string                   Address for the daemon to bind (not applicable in --dev mode) (default "0.0.0.0:8090")
      --cors-allow-credentials        Allow credentials in CORS requests
      --cors-allow-header strings     Allowed CORS request header (can be repeated) (default [Accept,Accept-Language,Content-Language,Content-Type,Range])
      --cors-allow-method strings     Allowed CORS request method, e.g. 'GET' (can be repeated) (default [GET,POST,PUT,DELETE,OPTIONS])
      --cors-allow-origin strings     Allowed CORS origin (can be repeated)
      --cors-enable                   Enable Cross-Origin Resource Sharing (CORS) for browser clients.
      --cors-expose-header strings    CORS response headers that should be made available to scripts in the browser (can be repeated)
      --cors-max-age string           CORS preflight max age (e.g., '5m', '300s') (default "5m0s")
      --dev                           Run the daemon in development-focused mode
      --interval-mcp-health string    Time interval to wait between MCP server health check attempts; a unit is required (e.g. 30s, 1m) (default "10s")
      --timeout-api-shutdown string   Timeout to wait for graceful API server shutdown; a bare number is seconds (e.g. 15, 30s, 1m) (default "5s")
      --timeout-mcp-health string     Timeout to wait for completion of MCP server health checks; a bare number is seconds (e.g. 15, 30s, 1m) (default "3s")
      --timeout-mcp-init string       Timeout to wait per MCP server for initialization; a bare number is seconds (e.g. 15, 30s, 1m) (default "30s")
      --timeout-mcp-request string    Timeout to wait for MCP tool call requests; a bare number is seconds (e.g. 15, 30s, 1m) (default "15s")
      --timeout-mcp-shutdown string   Timeout to wait for shutdown of MCP servers; a bare number is seconds (e.g. 15, 30s, 1m) (default "5s")
```

## Options inherited from parent commands

```
      --config-file string    path to config file (default ".mcpd.toml")
      --log-level string      log level for mcpd logs (default "info")
      --log-path string       log file path to use for log output
      --runtime-file string   path to runtime (execution context) file that contains env vars, and arguments for your MCP servers (default "/home/runner/.config/mcpd/secrets.dev.toml")
```

## SEE ALSO

* [mcpd](/mcpd/cli-reference/mcpd.md) - `mcpd` CLI is the primary interface for developers to interact with, and configure `mcpd`

**Auto generated by spf13/cobra on 14-Aug-2026**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mozilla.ai/mcpd/cli-reference/mcpd_daemon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
