TeamSnap MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAMSNAP_CLIENT_ID | No | Your TeamSnap OAuth Client ID from the TeamSnap Developer Portal | |
| TEAMSNAP_MCP_ENDPOINT | No | The AWS API Gateway endpoint URL for the MCP server (e.g., https://your-api-id.execute-api.us-west-2.amazonaws.com/mcp) | |
| TEAMSNAP_REDIRECT_URI | No | The OAuth redirect URI (use a tunnel URL like https://your-tunnel-url/callback for local development) | |
| TEAMSNAP_CLIENT_SECRET | No | Your TeamSnap OAuth Client Secret from the TeamSnap Developer Portal |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| teamsnap_authB | Authenticate with TeamSnap. Opens a browser window for OAuth login. Credentials are loaded from environment variables (TEAMSNAP_CLIENT_ID, TEAMSNAP_CLIENT_SECRET) or can be passed as arguments. |
| teamsnap_auth_statusA | Check the current TeamSnap authentication status. Returns whether you are connected and user info if authenticated. |
| teamsnap_logoutA | Disconnect from TeamSnap and clear stored credentials. |
| teamsnap_list_teamsB | List all TeamSnap teams you have access to. Returns team names, IDs, sport, division, and season info. |
| teamsnap_get_teamC | Get detailed information about a specific team. |
| teamsnap_get_rosterB | Get the roster (players and coaches) for a team. Returns member names, jersey numbers, positions, and roles. |
| teamsnap_get_eventsB | Get events (games, practices, etc.) for a team. Optionally filter by date range. |
| teamsnap_get_eventC | Get detailed information about a specific event. |
| teamsnap_get_availabilityB | Get availability responses for an event. Shows who is available, unavailable, or hasn't responded. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as authentication (auth, auth_status, logout), event management (get_event, get_events, get_availability), and team/roster operations (list_teams, get_team, get_roster). There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
All tool names follow a consistent 'teamsnap_' prefix with a clear verb_noun pattern (e.g., teamsnap_get_event, teamsnap_list_teams). The naming is uniform throughout, using snake_case consistently without any deviations or mixed conventions, which enhances predictability and readability.
With 9 tools, the server is well-scoped for managing TeamSnap resources like authentication, teams, events, and rosters. Each tool serves a distinct and necessary function, avoiding bloat or thin coverage, making the count appropriate for the domain's typical operations.
The tool set provides strong coverage for core TeamSnap workflows, including authentication, listing and retrieving teams, events, and rosters, with event availability as a bonus. Minor gaps exist, such as no tools for creating or updating events, teams, or roster members, but agents can still perform essential read and authentication tasks effectively.