Gatherings MCP Server

Most developer tooling work still happens through a UI a human drives. Gatherings MCP server moves it into the conversation instead. Enables AI assistants to manage and track shared expenses within the Gatherings application via the Machine Conversation Protocol.

The short version

A Model Context Protocol server for managing gatherings and expense sharing.

The Gatherings MCP Server provides an API that allows AI assistants to interact with the Gatherings application through the Machine Conversation Protocol. This enables AI systems to help users manage shared expenses for social events, outings, or any gathering where costs are split among participants.

• Create and manage gatherings with multiple members
• Add expenses for specific members
• Calculate fair reimbursements
• Record payments and reimbursements
• Generate detailed payment summaries
• Add/remove members from gatherings

The tools it exposes

The server publishes 2 tools. What each one is for:

• Prerequisites — The Prerequisites tool exposed by this server
• Setup — 1. Clone this repository: bash git clone https://your-repository.git cd accel

What it needs from you

Configuration is passed through the environment: GATHERINGS_DB_PATH, GATHERINGS_SCRIPT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Python 3.8+ - SQLAlchemy - MCP SDK

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Gatherings's toolset — Prerequisites, Setup — is a fair guide to whether it matches your workflow. It is maintained by abutbul; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.