Mcp Server

Agent-first meeting schedule polls for humans and agents. Create polls, vote, find times.

The Meetlark MCP Server provides an agent-first interface for managing meeting schedule polls. It is published by ai.meetlark, available via npm as @meetlark/mcp-server at version 1.0.3, and communicates over the stdio transport.

The server is described as agent-first, meaning it is built to work natively within automated agent workflows alongside human participants. Its stated capabilities cover three core operations: creating meeting schedule polls, casting votes on those polls, and finding times that work across participants.

An AI agent integrated with this server can initiate a scheduling poll on behalf of a user, record votes from multiple participants, and surface the results to determine a mutually available time slot. This covers the coordination loop that would otherwise require manual back-and-forth.

Because no tool list was provided in the registry record, the exact API surface cannot be described in detail. Developers should consult the npm package documentation for the specific tool names and parameters available in this version.

This server is a poor fit if the requirement is calendar synchronization, event creation in a calendar system, or video conferencing management — the scope is limited to poll-based scheduling coordination. It also requires a stdio-capable host environment.

Use cases

  • Create a meeting availability poll on behalf of a user within an agent workflow
  • Record and aggregate votes from multiple participants on proposed meeting times
  • Identify the best available time slot from poll responses
  • Automate scheduling coordination without human manual input

When to use it

  • An agent needs to coordinate meeting times across multiple participants
  • The workflow requires poll-based scheduling rather than direct calendar access
  • The host environment supports stdio transport
  • Scheduling needs to work for both human and automated participants

When not to use it

  • Direct calendar event creation or modification is required
  • Integration with a specific calendar provider (e.g. Google Calendar, Outlook) is needed
  • The host environment does not support stdio transport
  • Real-time availability lookup from calendar systems is necessary