Timergy MCP Server

MCP server for Timergy - create scheduling polls, vote, and finalize from AI agents like Claude, GPT, and Gemini. No authentication required. The timergy mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 8 defined tools rather than through you.

What it actually does

Timergy is a scheduling poll service (like Doodle or When2Meet). You create a poll with time slot options, share it with participants, everyone votes on their availability, and you pick the best time.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Its toolset

Everything the assistant can do here goes through one of these:

• Method — Endpoint
• POST — /api/open/polls
• GET — /api/open/polls/:id
• create_poll — Returns: poll URL (to share), passphrase (for admin access), option IDs
• get_poll — Get poll details and time slot options (no votes). Use this to retrieve option IDs before voting or finalizing
• vote_on_poll — Submit votes on a poll. Each vote maps a time slot to yes/maybe/no
• get_results — The get_results tool exposed by this server
• finalize_poll — Lock in the winning time slot. Notifies participants who provided an email

Configuration

You will need one environment variable: TIMERGY_API_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the timergy mcp server does with a few real requests.

When to reach for it

This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Timergy's toolset — Method, POST, GET and 5 more — is a fair guide to whether it matches your workflow. It is maintained by timergy-app; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.