Schema | people-mcp

people-mcp

Describes the environment variables required to run the server.

Name	Required	Description
`SEED_DEMO`	No	Controls whether demonstration data is indexed on first startup. Set to `false` to start with an empty index. Defaults to `true` (demo data is seeded).
`WRITE_TOKEN`	Yes	A long random secret used as the bearer token for publishing and updating profiles/projects. Required before first startup. Generate with `openssl rand -hex 32`.
`BIND_ADDRESS`	No	The IP address the API server binds to. Default is `127.0.0.1`. Use behind a TLS reverse proxy.
`MCP_ALLOWED_HOSTS`	No	Comma-separated list of allowed Host headers, including port wildcards if needed. Example: `localhost:,127.0.0.1:,api:*,people.example.com`. Used to protect against DNS rebinding when exposing the MCP server.
`POSTGRES_PASSWORD`	Yes	The password for the PostgreSQL database role. Required before first startup. Generate with `openssl rand -hex 32`. Changing it later requires updating the existing PostgreSQL role as well.
`MCP_ALLOWED_ORIGINS`	No	Comma-separated list of allowed browser origins for CORS. Example: `http://localhost:,http://127.0.0.1:,https://people.example.com`. Only needed for browser-based clients; most non-browser MCP clients do not send an Origin header.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityMaintained

ResponsivenessNo issues