SERVER

TimeZest

Rank #9,080

io.github.WYRE-AI/timezest-mcp

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

13 versions

by wyre-technology (60 servers)View repository ↗

First listed

May 22, 2026

Last publish date

Oct 14, 2026

PURPOSE

What you can do with TimeZest

TimeZest is a Model Context Protocol (MCP) server published by wyre-technology. It ranks #9,080 of 144,396 active servers on MCP Toplist. TimeZest is listed across 3 registries — Official MCP, Glama and PulseMCP, with 13 tracked versions. It was first listed on May 22, 2026 and most recently updated on Oct 14, 2026.

Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.

CAPABILITIES AND LIMITATIONS

What TimeZest can and cannot do

Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.

REQUIREMENTS

What you need before using TimeZest

DeclaredAPI keyCredentials declared

The registry listing declares required configuration before first use — typically an API key, token or connection string set via environment variables.

Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.

Declared in the registry install config

TIMEZEST_API_TOKEN · required
MCP_TRANSPORT · optional
AUTH_MODE · optional
LOG_LEVEL · optional

INSTALLATION AND FIRST TASK

Connect TimeZest and confirm it works

Docker image

claude mcp add timezest-mcp -e "TIMEZEST_API_TOKEN=<your TIMEZEST_API_TOKEN>" -e "MCP_TRANSPORT=<your MCP_TRANSPORT>" -e "AUTH_MODE=<your AUTH_MODE>" -e "LOG_LEVEL=<your LOG_LEVEL>" -- docker run -i --rm ghcr.io/wyre-ai/timezest-mcp:v3.0.2

Replace each placeholder with your own value before saving.

Docker image

[mcp_servers.timezest-mcp]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"]

[mcp_servers.timezest-mcp.env]
TIMEZEST_API_TOKEN = "<your TIMEZEST_API_TOKEN>"
MCP_TRANSPORT = "<your MCP_TRANSPORT>"
AUTH_MODE = "<your AUTH_MODE>"
LOG_LEVEL = "<your LOG_LEVEL>"

Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.

Docker image

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

Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.

Docker image

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

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.

Docker image

{
  "servers": {
    "timezest-mcp": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/timezest-mcp:v3.0.2"
      ],
      "env": {
        "TIMEZEST_API_TOKEN": "<your TIMEZEST_API_TOKEN>",
        "MCP_TRANSPORT": "<your MCP_TRANSPORT>",
        "AUTH_MODE": "<your AUTH_MODE>",
        "LOG_LEVEL": "<your LOG_LEVEL>"
      }
    }
  }
}

Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.

Docker image

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

Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.

Docker image

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

Replace each placeholder with your own value before saving.

First successful task

After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.

ALTERNATIVES

When to choose another server

Other servers by wyre-technology

View all wyre-technology servers →

No task-specific alternatives are catalogued for TimeZestyet; the list above is its publisher's other servers.

MAINTENANCE AND EVIDENCE

What changed, and when this was checked

First listed: May 22, 2026
Latest version published: Oct 14, 2026
Version history: 13 versions tracked (below)
Requirements evidence: Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
Profile checked: Not yet — purpose, capabilities and requirements above come from registry data only
Ranking data as of: Oct 16, 2026

Registry sightings

Glama ↗listed since May 27, 2026 · delisted, last seen Aug 26, 2026
PulseMCP ↗listed since May 31, 2026 · still listed
Official MCP ↗listed since Jul 18, 2026 · still listed
Official MCP ↗listed since Aug 27, 2026 · still listed
Glama ↗listed since Sep 4, 2026 · still listed

Do you maintain TimeZest? to correct or enrich this profile.

VERSIONS

Available versions (13)

Version	Published
3.0.2	Oct 14, 2026
3.0.1	Sep 25, 2026
3.0.0	Sep 17, 2026
2.0.1	Aug 26, 2026
1.2.6	Aug 11, 2026
1.2.5	Jul 21, 2026
1.2.4	Jul 21, 2026
1.2.3	Jul 21, 2026
1.2.2	Jul 20, 2026
1.2.1	Jul 20, 2026
1.2.0	Jul 17, 2026
1.1.2	Jul 2, 2026
1.1.1	May 29, 2026

STANDING

#9,080of 144,396 active serversTop 10%

Ranks ahead of 135,316 of 144,396 servers on MCP Toplist.

BADGE

Show your rank

Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.

Markdown

[![MCP Toplist](https://mcptoplist.com/badge/io.github.WYRE-AI%2Ftimezest-mcp.svg)](https://mcptoplist.com/server/io.github.WYRE-AI%2Ftimezest-mcp)

HTML

<a href="https://mcptoplist.com/server/io.github.WYRE-AI%2Ftimezest-mcp"><img src="https://mcptoplist.com/badge/io.github.WYRE-AI%2Ftimezest-mcp.svg" alt="MCP Toplist: Top 10% of 144,396" /></a>

Variants: append ?metric=score or ?metric=stars to the image URL.

FAQ

Frequently asked questions

Who maintains TimeZest?: TimeZest is maintained by wyre-technology, which publishes 60 MCP servers (872 total versions) tracked on MCP Toplist.
Is TimeZest listed on the Official MCP Registry?: Yes — TimeZest is listed on the Official MCP Registry, alongside Glama and PulseMCP.
How many versions does TimeZest have?: MCP Toplist tracks 13 versions of TimeZest, most recently published on Oct 14, 2026.
Where can I find the source code for TimeZest?: The source code for TimeZest is hosted at github.com/wyre-technology/timezest-mcp.

Used in projects

Do you run this server?

Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.

EXPLORE

All MCP Servers Official MCP Servers GitHub MCP Servers Best MCP Servers Most Active MCP Servers New MCP Servers Best New MCP Servers