TeamSnap MCP Server
Connects Claude to TeamSnap accounts to access teams, rosters, events, and availability data. Supports OAuth 2.0 authentication with optional AWS serverless deployment for permanent HTTPS callback URLs.
README
TeamSnap MCP Server
A Model Context Protocol (MCP) server that connects Claude to your TeamSnap account. Access your teams, rosters, events, and availability data directly from Claude Desktop or CLI.
Features
- Teams: List and view all your TeamSnap teams
- Rosters: Get player and coach information
- Events: View games, practices, and other events
- Availability: Check who's available for events
- Secure: OAuth 2.0 authentication with encrypted token storage
- AWS Deployment: Optional serverless deployment with permanent HTTPS callback URL
Quick Start
1. Get TeamSnap OAuth Credentials
- Go to TeamSnap Developer Portal
- Create a new application
- Set the redirect URI (see options below)
- Note your Client ID and Client Secret
2. Choose Your Deployment
Option A: Local MCP Server
For local development with a tunnel for OAuth callback.
git clone https://github.com/yourusername/TeamSnapMCP.git
cd TeamSnapMCP
npm install
npm run build
Add to Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"teamsnap": {
"command": "node",
"args": ["/path/to/TeamSnapMCP/dist/index.js"],
"env": {
"TEAMSNAP_CLIENT_ID": "your-client-id",
"TEAMSNAP_CLIENT_SECRET": "your-client-secret",
"TEAMSNAP_REDIRECT_URI": "https://your-tunnel-url/callback"
}
}
}
}
Redirect URI: Use a tunnel like cloudflared tunnel --url http://localhost:8374 for HTTPS callback.
Option B: AWS Serverless (Recommended)
Deploy to AWS Lambda for a permanent HTTPS callback URL with no tunnels needed.
cd aws
npm install
Set environment variables:
export AWS_ACCESS_KEY_ID=your-aws-key
export AWS_SECRET_ACCESS_KEY=your-aws-secret
export AWS_REGION=us-west-2
export TEAMSNAP_CLIENT_ID=your-client-id
export TEAMSNAP_CLIENT_SECRET=your-client-secret
Deploy:
node scripts/deploy.cjs
This creates:
- API Gateway with permanent HTTPS URL
- Lambda function for MCP server
- DynamoDB table for token storage
Then use the wrapper for Claude Desktop:
{
"mcpServers": {
"teamsnap": {
"command": "node",
"args": ["/path/to/TeamSnapMCP/dist/wrapper.js"],
"env": {
"TEAMSNAP_MCP_ENDPOINT": "https://your-api-id.execute-api.us-west-2.amazonaws.com/mcp"
}
}
}
}
3. Authenticate
Tell Claude: "Connect to TeamSnap"
A browser will open for OAuth login. Once complete, you're connected!
Available Tools
| Tool | Description |
|---|---|
teamsnap_auth |
Connect to TeamSnap |
teamsnap_auth_status |
Check connection status |
teamsnap_logout |
Disconnect from TeamSnap |
teamsnap_list_teams |
List all your teams |
teamsnap_get_team |
Get team details |
teamsnap_get_roster |
Get players and coaches |
teamsnap_get_events |
Get team events |
teamsnap_get_event |
Get event details |
teamsnap_get_availability |
Get event availability |
Example Prompts
- "What teams do I have in TeamSnap?"
- "Show me the roster for the Jr Kraken"
- "What games do we have scheduled this month?"
- "Who's available for Saturday's game?"
Architecture
┌─────────────────────────────────────────────────────────────┐
│ AWS (Optional) │
│ ┌──────────────┐ ┌──────────────┐ ┌───────────────┐ │
│ │ API Gateway │───▶│ Lambda │───▶│ DynamoDB │ │
│ │ (HTTPS) │ │ (MCP Server) │ │ (Tokens) │ │
│ └──────────────┘ └──────────────┘ └───────────────┘ │
└─────────────────────────────────────────────────────────────┘
▲
│ HTTP/SSE
▼
┌───────────┐ ┌───────────────┐
│ Wrapper │◀───────▶│ Claude Desktop│
│ (stdio) │ │ │
└───────────┘ └───────────────┘
Security
- OAuth tokens encrypted with AES-256-GCM (local) or stored in DynamoDB (AWS)
- Only read access requested from TeamSnap
- No credentials stored in code
Development
# Install dependencies
npm install
# Build
npm run build
# Run locally
node dist/index.js
# Run wrapper (connects to AWS)
node dist/wrapper.js
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
E2B
Using MCP to run code via e2b.