Productivity
meetingpoll.com
An MCP server for creating meeting scheduling polls, collecting participant availability votes, and analyzing consensus to recommend the optimal meeting slot.
ENDPOINT 1
https://api.meetingpoll.com/mcp
MCP server metadata
- Name
- MeetingPoll Connector
- Version
- 1.0.0
Known tools 3
create_meeting_pollAgentic tool to create a new meeting scheduling poll with candidate dates, time slots, duration, and optional invitee emails
Potential side effectsget_poll_consensusAnalyze vote distribution and calculate optimal meeting slot with percentage agreement, voter breakdown, and AI scheduling recommendations
Inferred read-onlysubmit_participant_voteSubmit availability votes for a participant on candidate meeting slots
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.meetingpoll-connector]
url = "https://api.meetingpoll.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"meetingpoll-connector": {
"type": "http",
"url": "https://api.meetingpoll.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: meetingpoll-connector
Remote MCP URL: https://api.meetingpoll.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"meetingpoll-connector": {
"url": "https://api.meetingpoll.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"meetingpoll-connector": {
"type": "http",
"url": "https://api.meetingpoll.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "meetingpoll-connector",
"transport": "streamable-http",
"url": "https://api.meetingpoll.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.