mcpField
L
Life Dashboard

Life Dashboard

Local
github.comHealth7Updated 1d ago
RepositoryVisit website

About Life Dashboard

Read-only health and screen time history from the Postgres of a self-hosted Life Dashboard Stack

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "owen282000-life-dashboard": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PGHOST",
        "-e",
        "PGDATABASE",
        "-e",
        "PGUSER",
        "-e",
        "PGPASSWORD",
        "ghcr.io/owen282000/life-dashboard-mcp:1.2.0"
      ],
      "env": {
        "MCP_TRANSPORT": "<MCP_TRANSPORT>",
        "PGHOST": "<PGHOST>",
        "PGDATABASE": "<PGDATABASE>",
        "PGUSER": "<PGUSER>",
        "PGPASSWORD": "<PGPASSWORD>"
      }
    }
  }
}
Run commanddocker run -i --rm -e MCP_TRANSPORT -e PGHOST -e PGDATABASE -e PGUSER -e PGPASSWORD ghcr.io/owen282000/life-dashboard-mcp:1.2.0
Environment variables to set
MCP_TRANSPORTServes MCP on stdio. Over Streamable HTTP, with a bearer token, the stack runs it itself: see docs/mcp.md.
PGHOSTThe stack's Postgres: db on the stack's Docker network.
PGDATABASEThe stack's database.
PGUSERdash_ro, the stack's user that can only read the dash views.
PGPASSWORDSecretThe password of dash_ro: DASH_DB_PASSWORD in the stack's .env.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocighcr.io/owen282000/life-dashboard-mcp:1.2.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.