Open MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_GENERATIVE_AI_API_KEY | Yes | Required for AI summarization features |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_fileD | – |
| write_fileD | – |
| list_directoryD | – |
| search_filesD | – |
| fetch_urlD | – |
| scrape_htmlD | – |
| git_statusD | – |
| git_logD | – |
| git_diffD | – |
| system_infoD | – |
| get_timeD | – |
| summarizeD | – |
| list_promptsC | List all available prompt templates, optionally filtered by category |
| search_promptsC | Search for prompt templates by query string |
| get_promptB | Get a prompt template by ID with its parameters and examples |
| render_promptC | Render a prompt template with the given parameters |
| validate_promptB | Validate parameters against a prompt template without rendering |
| get_prompt_categoriesB | Get all available prompt categories |
| execute_workflowC | Execute a workflow by ID with optional variables |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| prompts | |
| skills | |
| workflows | |
| server-info |
TDQS
Scored across 19 tools
Most tools have distinct purposes, with clear separation between prompt management (get_prompt, list_prompts, render_prompt, validate_prompt), file operations (read_file, write_file, list_directory, search_files), git operations (git_diff, git_log, git_status), and utility functions (get_time, system_info, summarize). However, some tools like fetch_url and scrape_html could potentially overlap in web-related tasks, and the lack of descriptions for many tools creates minor ambiguity.
The naming follows a generally consistent verb_noun pattern (e.g., execute_workflow, get_prompt, list_directory, read_file), which is good. However, there are inconsistencies: some tools use underscores (git_diff) while others might imply similar patterns but lack clarity due to missing descriptions (e.g., summarize, system_info). The overall pattern is readable but not perfectly uniform.
With 19 tools, the count is on the higher side but still reasonable for a general-purpose 'Open MCP Server' aiming to cover multiple domains like workflows, prompts, file operations, git, and utilities. It feels slightly heavy, as some tools could be consolidated (e.g., multiple prompt-related tools), but it's not excessive and aligns with a broad scope.
The server covers several domains: prompt management has good coverage (list, get, render, validate, search), file operations are basic but functional (read, write, list, search), and git operations provide core commands. However, there are gaps: for workflows, only execute_workflow exists without tools for listing or managing workflows, and utility tools like fetch_url and scrape_html lack descriptions, making it hard to assess their coverage. Overall, it's moderately complete but has notable omissions.