Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APP_ENVYesApplication environment (e.g., development, production)
LOG_LEVELNoLogging level (applied at bootstrap via configure_logging())
REDIS_URLNoRedis connection URL (required when CACHE_ENABLED=true)
GROQ_API_KEYNoOptional API key for Groq LLM (lazy-init at first use)
SUPABASE_URLYesSupabase project URL
CACHE_ENABLEDNoSet to 'true' to enable caching in production
TAVILY_API_KEYNoOptional API key for Tavily search
YOUTUBE_API_KEYYesYouTube Data API v3 key
SUPABASE_SERVICE_ROLE_KEYYesSupabase service role key (secret)

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

CapabilityDetails
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

NameDescription
health_checkA

Verify the MCP server is running.

search_youtubeC

Search for educational YouTube videos matching a query.

find_documentsB

Retrieve educational documents enriched with complementary videos.

run_workflowC

Execute the document + video discovery LangGraph workflow.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

Tools are distinct: health_check is server status, search_youtube targets only videos, find_documents focuses on documents with videos, and run_workflow executes a combined workflow. Minimal overlap.

Naming Consistency4/5

All tools use snake_case with a verb_noun pattern, though health_check is noun_verb. The pattern is consistent and readable.

Tool Count2/5

With 4 tools, the server feels too sparse for an 'ed-tech system.' The core functionality (search, documents, workflow) is minimal, leaving many expected operations uncovered.

Completeness2/5

The server lacks CRUD operations for resources, user management, and other typical ed-tech features. The tool set is focused on discovery only, which is incomplete for the broad server name.

Maintenance

ActivityActive
ResponsivenessNo issues