Boostcamp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_my_profileA | Get the current user's profile and settings from Boostcamp. |
| list_enrolled_programsA | List all fitness programs the user is currently enrolled in. |
| get_training_historyC | Get the user's training history. Default timezone offset is -300. |
| get_payment_historyB | Get the user's payment history. |
| list_custom_exercisesA | List the custom exercises created by the user. |
| list_all_programsB | List all available programs with pagination and optional keyword search. |
| get_program_detailsB | Get detailed information about a specific program by its ID. |
| list_blogsC | List blog posts with pagination. |
| get_home_summaryC | Get dashboard summary statistics (total workouts, weight, streak). |
| get_home_programsC | Get a summary of active/recent user programs. |
| get_home_chartC | Get training volume chart data. |
| get_home_muscleC | Get muscle group distribution data. |
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 12 tools
Most tools have clear distinct purposes, but there is slight overlap between 'get_home_programs' (summary of active/recent programs) and 'list_enrolled_programs' (all enrolled programs), and between 'get_home_summary' and 'get_training_history' which both provide training data.
All tool names follow a consistent verb_noun pattern with snake_case: get_* for fetching single items, list_* for collections. No mixing of styles.
12 tools is an appropriate number for a fitness dashboard MCP server, covering home stats, programs, exercises, blogs, profile, and payment without being overwhelming or too sparse.
The tool surface covers read operations well for dashboard, programs, training history, and user data. Minor gaps exist (no write tools like create/update programs or exercises), but the server appears focused on data retrieval, which is reasonable.