StudyPilot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FAISS_DIR | No | Set FAISS_DIR only when the index must live elsewhere, such as an isolated test or deployment data volume. | data/faiss/ |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_materialsB | Search course materials with dense plus lexical reciprocal-rank fusion. |
| get_documentA | Read a complete course document using its document ID. |
| create_study_taskC | Create a study task. Use an ISO 8601 date-time when a deadline is needed. |
| list_study_tasksA | List study tasks, optionally filtered by their current status. |
| update_study_task_statusB | Set a study task status to pending, in_progress, or completed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| study_quiz | Create instructions for a source-grounded course quiz. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| course_catalog | List the course documents currently available to StudyPilot. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: searching materials, fetching a document by ID, and creating/list/updating task status. No overlapping responsibilities or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (search_materials, get_document, create_study_task, list_study_tasks, update_study_task_status). The slight plural/singular variation is semantically appropriate and does not break the pattern.
With 5 tools, the server is well-scoped: two for material retrieval and three for task management. Each tool earns its place without redundancy or bloat.
The core workflows are covered: searching and reading materials, plus creating, listing, and updating task status. Minor gaps exist, such as lack of delete or full task edit (e.g., changing deadline), but these can be worked around.