Schema | Email MCP Server

Email MCP Server

Describes the environment variables required to run the server.

Name	Required	Description	Default
`EMAIL_ACCOUNTS`	No	JSON describing accounts, passed directly via the client config `env` field instead of using a config file.
`MCP_EMAIL_ADDRESS`	No	Email address for single-account mode (no config file needed).
`MCP_EMAIL_PASSWORD`	No	Password or app password for single-account mode (no config file needed).
`EMAIL_MCP_HTTP_HOST`	No	Address to bind when running as a Streamable HTTP server (flag: --host).	127.0.0.1
`EMAIL_MCP_HTTP_PATH`	No	HTTP path serving MCP when running as a Streamable HTTP server (flag: --path).	/mcp
`EMAIL_MCP_HTTP_PORT`	No	Port to listen on when running as a Streamable HTTP server (flag: --port).	8080
`MCP_EMAIL_IMAP_HOST`	No	IMAP server host for single-account mode, e.g. imap.gmail.com.
`MCP_EMAIL_SMTP_HOST`	No	SMTP server host for single-account mode, e.g. smtp.gmail.com.
`EMAIL_MCP_HTTP_TOKEN`	No	Bearer token required on every HTTP request; empty means no auth (loopback only). Essentially required by `docker compose --profile http up`.
`EMAIL_MCP_HTTP_ALLOWED_HOSTS`	No	Comma-separated Host header allowlist (DNS-rebinding protection); `*` disables the check. Defaults to loopback names plus the bind host (flag: --allowed-hosts).

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

ActivityActive

ResponsivenessNo issues