LearnMCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment (development, production) | |
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | |
| FOREST_DATA_DIR | Yes | Shared data directory with Forest |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_learning_sourcesC | Add learning sources (URLs) to a project for content extraction and summarization |
| process_learning_sourcesC | Start background processing of pending learning sources for a project |
| list_learning_sourcesC | List learning sources for a project, optionally filtered by status |
| get_learning_summaryC | Get learning content summary for a project or specific source |
| delete_learning_sourcesC | Delete learning sources and their summaries from a project |
| get_processing_statusC | Get current processing status for learning sources in a project |
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 6 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, add_learning_sources, delete_learning_sources, and list_learning_sources handle source management, while get_learning_summary, get_processing_status, and process_learning_sources focus on content processing and status. The descriptions reinforce these distinct roles, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern using snake_case, such as add_learning_sources, delete_learning_sources, and get_learning_summary. This uniformity enhances readability and predictability, allowing agents to easily infer functionality from the naming convention without confusion.
With 6 tools, the server is well-scoped for managing learning sources and summaries. Each tool earns its place by covering essential operations like adding, deleting, listing, processing, and retrieving status and summaries. This count is neither too sparse nor bloated, fitting the domain appropriately.
The tool set provides comprehensive coverage for the learning source domain, including CRUD-like operations (add, delete, list), processing, and status/summary retrieval. A minor gap exists in update functionality for learning sources, but agents can work around this by deleting and re-adding. Overall, the surface supports core workflows effectively.