Timergy MCP Server

Source-reviewed, not functionally tested

These details were checked against primary sources. Skill Road has not performed a practical client functionality test. Features and setup reflect project documentation, not independently confirmed operation.

Turn a scheduling discussion into a shared poll

Timergy MCP Server connects an AI client to the Timergy scheduling service. The provider distributes the integration as @timergy/mcp. It is useful for teams, community groups and project organizers who need to collect availability before choosing a meeting time. Instead of stopping at a suggested invitation message, an assistant can work with actual scheduling objects. The value is a clearer handoff from a conversation about possible dates to a poll that participants can review themselves.

Start with a plan, then permit the action

A sensible request specifies the purpose of the meeting, its duration, candidate dates and the participants' time zones. Ask the assistant to restate those details before creating anything. Inspect the resulting poll link before sharing it with colleagues. This small checkpoint catches misunderstandings that would otherwise become invitations to the wrong meeting. For recurring activities, use a distinct title and explicit dates rather than relying on the assistant to infer which occurrence you mean.

The documented tools cover poll creation, voting, result retrieval and finalization. Account-related operations add personal polls, contacts and calendar-conflict information. These capabilities are not all read-only. Sending reminders affects real participants, while finalizing a poll changes its state. Separate analysis from permission to act: a suggestion that one option is popular should not automatically authorize sending messages or committing everyone to it. The person organizing the meeting still owns the decision and any exceptions.

Choose the connection model deliberately

The package documentation describes local stdio and remote Streamable HTTP connections. Local operation needs a suitable Node.js environment; the hosted endpoint removes that installation step. Neither arrangement turns Timergy into an offline scheduling application. A local MCP process still calls the external service. Organizations handling personal invitation data should assess where titles, dates and contact information are sent before enabling the integration in a shared assistant environment.

Understand free access and account permissions

The MCP package carries an MIT license. Timergy says its integrations work on the free service tier, while additional product features may require paid plans. An open poll does not necessarily require a user account, but protected account operations need the documented credentials. Pick the smallest useful capability set. A basic availability poll rarely justifies exposing an entire contact directory or connected calendar. Free software licensing, hosted service limits and the cost of your AI client are separate considerations.

Questions worth answering before the first real meeting

Are dates and time zones unambiguous? Have you checked the recipient list? Who may finalize or reopen the poll? Treat administration passphrases as credentials rather than harmless links. Keep confidential calendar details out of shared conversations and review any tool that changes data before approving it. A disposable poll without real invitations is a good starting point. This integration supports scheduling work; it does not guarantee that the assistant understands every organizational constraint or that participants have agreed to an automatically selected option.

Source review and verification limits

This entry was reviewed against the linked primary sources on 2 October 2026. Features and setup instructions reflect the project's documentation rather than a complete functional test performed by Skill Road. Before production use, connect with non-sensitive example data, inspect the enabled tools, and compare responses with their original source. Changes to the service or your client may require a fresh review. The review date is not an uptime guarantee.

An MCP client; local operation requires Node.js 18 or newer and npm. Network access to Timergy. Account features need an appropriate API key or OAuth authorization.

Add a local stdio entry with command npx and args ["@timergy/mcp@0.6.3"]. Alternatively connect the documented HTTP endpoint https://api.timergy.com/mcp. Start with a test poll without real invitations.

npx @timergy/mcp@0.6.3

Open polls can be used without an account. Account operations need an API key or OAuth; open-poll administration uses the passphrase returned at creation. Some tools accept credentials as arguments.

Reads polls and results; can create polls, vote, send invitations and reminders, and finalize meetings. Account tools can read contacts and calendar conflicts, and modify or archive polls.

Poll titles, time slots, votes and optional contact details are sent to Timergy. Running the MCP software locally does not keep polls local. Results and possibly passphrases enter the client context.

Require confirmation for writes and notifications. Do not put passphrases or API keys in shared chats or committed configurations. Expose calendar information only with suitable permissions.