partiful-mcp
Related Servers
Alternatives to partiful-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceProvides read-only tools for discovering, searching, and browsing events from Luma, Posh, and Partiful platforms, including event details and guest lists, with optional authenticated access to a user's Luma events.10MIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that dynamically sources global technology events, communities, and niche networking mixers from Luma, Eventbrite, Meetup, and fallback search sources, enabling event discovery and community finding via natural language.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for automating Meetup event tracking with an AI agent. It equips the agent with tools to browse Meetup.com, detect new events since the last known record, and return structured event data.10 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for AgentFolio — the identity and reputation layer for AI agents. Query agent profiles, trust scores, verification status, and marketplace listings through 8 MCP tools.962 npm1MIT
- FlicenseNot gradedqualityCmaintenanceAn OAuth-secured remote MCP server (22 tools) that lets Claude, ChatGPT, and Codex search All-In Summit attendee profiles, explore the live agenda, check sessions and meetings, detect scheduling conflicts, and export a calendar. Account-changing actions are only prepared for review, with the user confirming each request in the browser before any event API call is made.-
- AlicenseBqualityBmaintenanceAn MCP server that gives AI agents a private, durable memory of people, providing a personal people graph in PostgreSQL with tools to search, remember, and connect people, plus imports from LinkedIn, Google Contacts, and WhatsApp, and a browser UI.111MIT
TDQS
Scored across 41 tools
Many tools have overlapping purposes, especially the 8+ event-list getters (get_my_rsvps, get_my_upcoming_events_for_home_page, get_my_past_events_for_home_page, get_published_events, get_discoverable_events, get_my_saved_events, get_my_followed_events). Detailed descriptions help disambiguate, but the sheer number of similar-sounding tools makes misselection likely.
All 40 read tools follow the get_<noun> pattern, and the sole write tool uses mark_<noun>_as_<state>. The naming is uniform and predictable, with no mixed conventions.
41 tools is excessive for the apparent scope. Many tools are extremely granular (ticket-related tools split across 5 separate getters, event lists split across 8 getters). The count could likely be reduced to 15-20 useful tools without losing functionality.
The tool surface is almost entirely read-only. There are no create/update/delete operations for events, contacts, or communities, no RSVP actions, no invite sending, and no comment posting. Only one write action exists (mark notifications read), which is a severe gap for an event-management platform.