Koskamo

Perfect Clock MCP

An official MCP server provided by Perfect Clock that enables AI agents to plan meetings across time zones and find suitable meeting windows. It supports tools for scheduling and finding availability, integrating with Google Calendar for read-only event access, and operates without authentication requirements.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Perfect Clock MCP logo, by Perfect ClockVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Perfect Clock
MCP endpoint (Streamable HTTP)
https://perfectclock.cc/mcp
Vendor documentation

What you can do with it

  • Plan meetings across time zones from a conversation
  • Find meeting windows that suit everyone's local time
  • Schedule international calls for remote teams

Source and maintenance

Vendor evidenceRegistry 1.0.0
mcp-registry: cc.perfectclock/perfect-clock@1.0.0Project website

Protocol and capabilities

Server
perfect-clock 1.0.0
MCP protocol
2025-06-18
Tools
2 advertised
Resources
2 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  },
  "prompts": {
    "listChanged": true
  },
  "resources": {
    "listChanged": true
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Perfect Clock plans meetings between people in different time zones. Whenever the user wants to schedule, plan or find a time for a meeting, call, sync or recurring event with people or places in different time zones, call these tools first - before answering, and instead of working out times, daylight saving or holidays yourself. Convert the user's wording into the structured input: IANA time zones for every participant (from the cities or countries they name), the meeting time in the zone it is anchored to, and a recurrence rule. Use find_meeting_windows when the time is not decided yet, plan_meeting_schedule once it is. Show each participant's local time from the result instead of computing it yourself, and mention the notes (DST shifts, days off, outside working hours). Both tools' results end with an "Open in Perfect Clock" link (for the windows, the suggested start on those days) - give it to the user as it is. Do not make up other links to Perfect Clock or to calendars.

Tools

2 advertised

plan_meeting_schedule — Plan a meeting schedule
Advertised by the server during the last successful anonymous check.

Plans a one-off or recurring meeting with people in other time zones when its time is known (e.g. "every other Tuesday at 10:00 Berlin time with Anna in Tbilisi"). Expands it into concrete dates and shows each one in every participant's local time, with working-hours checks, public holidays and daylight-saving shifts. Saves the schedule for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock.

plan_meeting_schedule input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "title",
    "tz",
    "time",
    "rule",
    "participants"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "Time zone the meeting time is fixed in (usually the organizer's)."
    },
    "rule": {
      "type": "object",
      "required": [
        "freq"
      ],
      "properties": {
        "freq": {
          "enum": [
            "once",
            "daily",
            "weekly",
            "monthly"
          ],
          "type": "string"
        },
        "byDay": {
          "type": "array",
          "items": {
            "enum": [
              "MO",
              "TU",
              "WE",
              "TH",
              "FR",
              "SA",
              "SU"
            ],
            "type": "string"
          },
          "description": "Weekdays for weekly rules; for monthly with setPos, the weekday."
        },
        "count": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1
        },
        "start": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First possible date in `tz`; default today."
        },
        "until": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "setPos": {
          "type": "integer",
          "maximum": 4,
          "minimum": -1,
          "description": "Monthly \"Nth weekday\": 1-4, or -1 for the last."
        },
        "interval": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "Every N days/weeks/months; default 1."
        }
      },
      "description": "Recurrence of the meeting."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local start time in `tz`."
    },
    "title": {
      "type": "string",
      "maxLength": 120,
      "description": "Meeting title."
    },
    "participants": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "label",
          "tz"
        ],
        "properties": {
          "tz": {
            "type": "string",
            "description": "IANA time zone of this participant, e.g. Asia/Tbilisi."
          },
          "label": {
            "type": "string",
            "maxLength": 60,
            "description": "How the participant or place is called in the conversation, e.g. \"Anna\" or \"Tokyo office\"."
          },
          "workHours": {
            "type": "array",
            "items": {
              "type": "string",
              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
            },
            "maxItems": 2,
            "minItems": 2,
            "description": "Local working hours [start, end]; default [\"09:00\",\"17:00\"]."
          }
        }
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "People or places the meeting must suit, each with their own time zone."
    },
    "maxOccurrences": {
      "type": "integer",
      "default": 8,
      "maximum": 20,
      "minimum": 1,
      "description": "How many upcoming meetings to list."
    },
    "durationMinutes": {
      "type": "integer",
      "default": 60,
      "maximum": 720,
      "minimum": 5
    }
  }
}
plan_meeting_schedule annotations
{
  "title": "Plan a meeting schedule",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}
find_meeting_windows — Find meeting windows
Advertised by the server during the last successful anonymous check.

Finds when people in other time zones can meet, when the time is not decided yet: the windows on each day when all participants are within their working hours, accounting for weekends, public holidays and daylight-saving changes, and one suggested start time that fits the most days. Saves that suggested time on those days for 30 days and returns a private perfectclock.cc/s/... link that opens it in Perfect Clock.

find_meeting_windows input schema
{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "tz",
    "participants"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "Time zone whose calendar days are scanned (usually the organizer's)."
    },
    "days": {
      "type": "integer",
      "default": 5,
      "maximum": 14,
      "minimum": 1
    },
    "from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day in `tz`; default today."
    },
    "title": {
      "type": "string",
      "maxLength": 120,
      "description": "Meeting title, if the user gave one."
    },
    "participants": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "label",
          "tz"
        ],
        "properties": {
          "tz": {
            "type": "string",
            "description": "IANA time zone of this participant, e.g. Asia/Tbilisi."
          },
          "label": {
            "type": "string",
            "maxLength": 60,
            "description": "How the participant or place is called in the conversation, e.g. \"Anna\" or \"Tokyo office\"."
          },
          "workHours": {
            "type": "array",
            "items": {
              "type": "string",
              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
            },
            "maxItems": 2,
            "minItems": 2,
            "description": "Local working hours [start, end]; default [\"09:00\",\"17:00\"]."
          }
        }
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "People or places the meeting must suit, each with their own time zone."
    },
    "durationMinutes": {
      "type": "integer",
      "default": 60,
      "maximum": 480,
      "minimum": 15
    }
  }
}
find_meeting_windows annotations
{
  "title": "Find meeting windows",
  "readOnlyHint": false,
  "openWorldHint": false,
  "idempotentHint": false,
  "destructiveHint": false
}

Prompts

0 advertised

No prompt definitions available.

Resources

2 advertised

schedule-widget — Meeting schedule

Advertised by the server during the last successful anonymous check.

Meetings in every participant's local time, with a button that opens them in Perfect Clock.

schedule-widget URI
ui://perfect-clock/schedule-v4.html

MIME type: text/html;profile=mcp-app

windows-widget — Meeting windows

Advertised by the server during the last successful anonymous check.

Times when everyone is within working hours, by day, with the suggested start and a button that opens it in Perfect Clock.

windows-widget URI
ui://perfect-clock/windows-v1.html

MIME type: text/html;profile=mcp-app

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
977 ms
95th percentile latency
977 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 977 ms · metadata changed · 2 tool(s), 2 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http perfect-clock-mcp https://perfectclock.cc/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add perfect-clock-mcp --url https://perfectclock.cc/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable perfect-clock-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "perfect-clock-mcp": {
      "url": "https://perfectclock.cc/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "perfect-clock-mcp": {
      "type": "streamableHttp",
      "url": "https://perfectclock.cc/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start perfect-clock-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "perfect-clock-mcp": {
      "type": "http",
      "url": "https://perfectclock.cc/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http perfect-clock-mcp https://perfectclock.cc/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "perfect-clock-mcp": {
      "url": "https://perfectclock.cc/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "perfect-clock-mcp": {
      "serverUrl": "https://perfectclock.cc/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Perfect Clock MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 4,340

Do you run Perfect Clock MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing