Skip to main content
Glama
standshare-mcp

standshare-mcp

by GraditiPro

standshare-mcp

CI CodeQL Socket Badge npm version License: MIT MCP SDK

An MCP (Model Context Protocol) server for the StandShare API. Gives Claude and other MCP clients composable tools for managing fundraising events, families, workers, finances, notifications, and reports within a StandShare organization.

StandShare is a family fundraising platform where organizations manage concession stand events, assign workers, track attendance, and distribute earnings to family accounts.

Security notice. Earlier versions of this README showed https://api.standshare.com. StandShare does not own that domain. If you used that URL, revoke the API key you configured in StandShare (/admin/org-settings/api-keys) and create a new one. If you signed in with an email and password instead, change that password. From 1.0.1 the server refuses any STANDSHARE_API_URL that is not a StandShare host.


Tools

Tool

Description

events

Search, view, create, and update fundraising events; add stands

families

Search, view (with balance), create families; add members

users

Search, view, create, and invite user accounts

venues

Search and view venue details

finances

Family balances, event revenue, transactions, settlement templates (read-only)

workers

Event rosters, assign workers, update attendance, check availability, view history

notifications

List notifications and send to individual users

reports

Admin dashboard KPIs, financial summaries, family compliance status

Money is never moved through this server. Settlement, account credits and scholarships are recorded in the StandShare web app.

Related MCP server: srgplus-mcp

Resources

URI

Description

standshare://guide

Domain guide covering the entity model, financial model, and migration playbook


Replacement

The hosted StandShare MCP server at https://api.standshare.app/mcp is the supported way to connect an MCP client to StandShare. Sign in with OAuth.


Installation

Claude Desktop

Add the following to your claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

API token

{
  "mcpServers": {
    "standshare": {
      "command": "npx",
      "args": ["-y", "@graditipro/standshare-mcp"],
      "env": {
        "STANDSHARE_API_URL": "https://api.standshare.app",
        "STANDSHARE_TENANT_SLUG": "your-org-slug",
        "STANDSHARE_API_TOKEN": "your-api-token"
      }
    }
  }
}

After editing, restart Claude Desktop. Verify the server loaded via the hammer icon (🔨) in the toolbar.

Other MCP Clients

Run directly:

STANDSHARE_API_URL=https://api.standshare.app \
STANDSHARE_TENANT_SLUG=your-org-slug \
STANDSHARE_API_TOKEN=your-api-token \
npx @graditipro/standshare-mcp

Environment Variables

Variable

Required

Description

STANDSHARE_API_URL

Yes

https://api.standshare.app. Only StandShare hosts (standshare.app and its subdomains) and localhost / 127.0.0.1 / [::1] for local development are accepted

STANDSHARE_TENANT_SLUG

Yes

Your organization's tenant slug

STANDSHARE_API_TOKEN

Yes

API key created in StandShare at /admin/org-settings/api-keys


Authentication

Set STANDSHARE_API_TOKEN. The token is sent as a Bearer header on every request. Email and password sign-in was removed in 1.0.1.


Local Development

git clone https://github.com/GraditiPro/standshare-mcp.git
cd standshare-mcp
npm install
npm run build

To run from a local build in Claude Desktop, replace "npx", ["-y", "@graditipro/standshare-mcp"] with:

{
  "command": "node",
  "args": ["/absolute/path/to/standshare-mcp/build/index.js"]
}

License

MIT

Available Tools

8 tools
eventsB

Manage fundraising events — search, view details, create, update, and add stands. Events are concession stand shifts at venues where families send workers to earn commissions.

Inputs: action (required), date, name, notes, +13 more.

familiesB

Manage family units — search, view details with balance, create, and add members. Families are the core unit in StandShare — they send workers to events and earn commissions to their family account.

Inputs: action (required), role, query, status, +5 more.

financesC

Financial operations — view family balances, event revenue, transactions, run settlement, and record historical data. Families earn commissions from events which are distributed to their accounts after settlement.

Inputs: action (required), date, type, limit, +11 more.

notificationsB

Send and view notifications — send messages to individual users, list notifications, and broadcast announcements to the organization.

Inputs: action (required), title, userId, message, +1 more.

reportsA

View organizational reports — admin dashboard with KPIs, financial summaries for date ranges, and compliance status showing which families are missing required documents.

Inputs: action (required), dateTo, dateFrom, familyId.

usersB

Manage user accounts — search, view details with roles and family associations, create, and invite. Users are individuals who log into StandShare and may be associated with one or more families.

Inputs: action (required), role, email, phone, +5 more.

venuesB

Look up venues — search by name/location and view details. Venues are physical locations (stadiums, arenas) where fundraising events take place.

Inputs: action (required), city, query, state, +1 more.

workersA

Manage worker assignments — view event rosters, assign workers to events/stands, update attendance, check availability, and view attendance history. Workers are family members who work concession stands at events.

Inputs: action (required), dateTo, userId, eventId, +8 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct domain (events, families, finances, etc.) with clear boundaries. No overlapping purposes; agents can easily differentiate.

    Naming Consistency5/5

    All tool names are single, plural nouns (e.g., events, families, users) following a consistent pattern. No mixed naming conventions.

    Tool Count5/5

    8 tools appropriately cover the core entities and operations of the StandShare system. Not too many or too few for the domain size.

    Completeness4/5

    Covers most key operations (CRUD on events, families, users; finances, reports, notifications). Minor gaps: no delete operations mentioned, venues only support search/view.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      C
      maintenance
      An MCP server for interacting with the USAspending.gov API, supporting local use with Claude Desktop and cloud deployment with login.gov authentication.
      3
      10
      -
    • A
      license
      A
      quality
      D
      maintenance
      A local MCP server that wraps the Housecall Pro Public API, enabling Claude to read and write Housecall Pro data (customers, jobs, estimates, invoices, etc.) via natural language.
      23
      174 npm
      MIT