MCP serverOfficial registry

TimeZest

MCP server for TimeZest — appointment scheduling, agents, appointment types, and resources for MSPs.

by io.github.WYRE-AIv3.0.1GitHub Website

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

docker run -i --rm ghcr.io/wyre-ai/timezest-mcp:v3.0.1

Credentials from the publisher

TIMEZEST_API_TOKEN — TimeZest API token (Bearer credential)
MCP_TRANSPORT — Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
AUTH_MODE — Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
LOG_LEVEL — Log verbosity: debug, info, warn, error

Provider

Claude Code

TIMEZEST_API_TOKEN=<secret> MCP_TRANSPORT=<value> AUTH_MODE=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-ai-timezest-mcp -- docker run -i --rm ghcr.io/wyre-ai/timezest-mcp:v3.0.1

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "io.github.wyre-ai-timezest-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.1"
      ],
      "env": {
        "TIMEZEST_API_TOKEN": "<secret>",
        "MCP_TRANSPORT": "<value>",
        "AUTH_MODE": "<value>",
        "LOG_LEVEL": "<value>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

TimeZest

Add this server

Host a copy with our keys and logs.

More like this

Firecrawl

Notion

Context7