standshare-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STANDSHARE_EMAIL | No | Admin email for credential-based auth | |
| STANDSHARE_API_URL | Yes | Base URL of your StandShare API instance | |
| STANDSHARE_PASSWORD | No | Admin password for credential-based auth | |
| STANDSHARE_API_TOKEN | No | API token for token-based auth | |
| STANDSHARE_TENANT_SLUG | Yes | Your organization's tenant slug |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| venuesB | Look up venues — search by name/location and view details. Venues are physical locations (stadiums, arenas) where fundraising events take place. |
| 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. |
| 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. |
| notificationsB | Send and view notifications — send messages to individual users, list notifications, and broadcast announcements to the organization. |
| reportsA | View organizational reports — admin dashboard with KPIs, financial summaries for date ranges, and compliance status showing which families are missing required documents. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| guide |
TDQS
Scored across 8 tools
Each tool targets a distinct domain (events, families, finances, etc.) with clear boundaries. No overlapping purposes; agents can easily differentiate.
All tool names are single, plural nouns (e.g., events, families, users) following a consistent pattern. No mixed naming conventions.
8 tools appropriately cover the core entities and operations of the StandShare system. Not too many or too few for the domain size.
Covers most key operations (CRUD on events, families, users; finances, reports, notifications). Minor gaps: no delete operations mentioned, venues only support search/view.