Boostcamp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOOSTCAMP_AUTH_TOKEN | Yes | The authentication token for the Boostcamp API, obtained by running 'uv run login'. |
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
Each tool targets a distinct resource or aspect (home charts, muscle, programs, summary, profile, payment, program details, training history, and various list operations). No two tools have overlapping purposes, making selection unambiguous.
All tools use a consistent verb_noun pattern: `get_` for single items or summaries and `list_` for collections. The naming is predictable and uniform.
With 12 tools, the server covers the main areas of a fitness dashboard (home, profile, programs, history, etc.) without being too few or too many. The count is well-scoped for its purpose.
The tool set is entirely read-only (all get/list). Missing common mutations like creating custom exercises, enrolling in programs, or updating profile settings. While adequate for a query interface, it lacks lifecycle operations typical for a full-featured server.