As autonomous AI agents, coding assistants, and conversational copilots become daily productivity drivers, group scheduling remains one of the last stubborn friction points. Coordinating 5 or 10 busy schedules across timezones often requires manual calendar cross-referencing, email chains, and tedious link swapping.
MeetingPoll solves this by introducing a native Model Context Protocol (MCP) Server and OpenAPI 3.0 tool suite. With MeetingPoll MCP, AI agents in Claude Desktop, Cursor, Gemini CLI, and custom Python/TypeScript agent frameworks can autonomously create polls, register participant availability votes, and calculate 100% unanimous consensus without leaving the chat interface.
What is the Model Context Protocol (MCP)?
The Model Context Protocol is an open standard developed by Anthropic that allows large language models (LLMs) to securely connect to external data sources, web services, and real-time tools. Rather than requiring brittle scraping or hardcoded function bindings, an MCP server provides standardized tool declarations, input validation schemas, and structured JSON-RPC communication.
By connecting your AI agent to MeetingPoll’s remote MCP server, your assistant gains direct access to live scheduling infrastructure. It can propose multi-day time slots, distribute branded invitations, monitor incoming votes, and notify you the moment consensus is reached.
MeetingPoll MCP Core Capabilities
MeetingPoll exposes three primary agentic tools designed specifically for multi-participant coordination:
create_meeting_poll
Creates live polls with candidate dates, start times, durations, and optional automatic email invites.
get_poll_consensus
Interrogates votes, calculates agreement percentages, identifies unanimous slots, and outputs recommendations.
submit_participant_vote
Registers participant availability directly on candidate slots programmatically or via agent delegation.
How to Connect Claude Desktop to MeetingPoll MCP
Integrating MeetingPoll into Claude Desktop takes less than 60 seconds:
- Open your Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
- Add the MeetingPoll remote server definition to the
mcpServersobject:
{
"mcpServers": {
"meetingpoll": {
"url": "https://api.meetingpoll.com/mcp"
}
}
}
- Restart Claude Desktop. The hammer icon will illuminate in the lower toolbar, confirming that
create_meeting_poll,get_poll_consensus, andsubmit_participant_voteare active.
Example Agent Prompts in Action
Once connected, you can converse with your agent naturally without worrying about API payload formatting:
Creating a Multi-Day Poll:
"Create a 45-minute MeetingPoll for our Architecture Review next Tuesday and Thursday between 10:00 AM and 3:00 PM, and send invitations to david@company.com and sarah@company.com."
Checking Group Consensus:
"Check poll consensus for poll ID 87fad220. If we have a unanimous time slot, summarize who voted and output the calendar invite details."
Why Developers & Remote Teams Choose MeetingPoll MCP
- Zero Voter Registration: When agents create polls, participants can vote immediately in their browser without being forced to download an app or log in.
- Automatic Timezone Normalization: The agent can operate in UTC while participants in Tokyo, London, and New York see proposed times translated to their local clocks.
- OpenAPI 3.0 & REST Compatibility: If you are building custom AI agents in LangChain, LlamaIndex, or AutoGen, MeetingPoll provides standard REST endpoints backed by an OpenAPI 3.0 schema at
https://api.meetingpoll.com/openapi.json.