TutorFlow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server. Usually set automatically by the platform (e.g. Render or Railway). | |
| DB_PATH | No | Path to the SQLite database file (defaults to a local `tutorflow.db` if not set). | |
| MCP_AUTH_TOKEN | No | Bearer token for authenticating `/mcp` requests. Recommended for both local HTTP and deployed servers. | |
| ANTHROPIC_API_KEY | No | API key for Anthropic. Used by the `generate_progress_report` tool. Optional for basic read/write tools. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_studentsA | List all students being tutored, with their grade and subject focus. Optionally filter by a search term matched against name or subject. |
| get_student_progressA | Get a student's recent session notes and open homework by student id. Use list_students first if you don't know the id. |
| log_session_noteA | Log a note for a tutoring session. By default this only PREVIEWS the note and does not save it — call again with confirm: true to actually write it. Use list_students first if you don't know the student_id. |
| assign_homeworkA | Assign a homework item to a student. By default this only PREVIEWS the assignment and does not save it — call again with confirm: true to actually create it. Use list_students first if you don't know the student_id. |
| generate_progress_reportA | Generate a parent-friendly progress summary for a student by having an LLM reason over their recent session notes and homework. Returns a draft by default — call again with save: true to store it in progress_notes. Requires ANTHROPIC_API_KEY. |
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 5 tools
Each tool targets a distinct action and resource: listing students, retrieving progress, logging session notes, assigning homework, and generating reports. No two tools could be confused for the same purpose.
All tool names follow a consistent verb_noun pattern (list_students, get_student_progress, log_session_note, assign_homework, generate_progress_report). The naming is uniform and predictable.
With 5 tools, the server is well-scoped for a tutoring workflow. Each tool covers a core operation without redundancy or bloat, fitting the ideal 3-15 range.
The tool surface covers the main lifecycle of tutoring: viewing students, accessing progress, adding session notes and homework, and producing reports. Minor gaps exist (no explicit update/delete for notes or homework), but agents can work around these by logging new notes or assignments.