MCP Server App
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub Personal Access Token for private repository access (optional) | |
| OPENAI_API_KEY | Yes | OpenAI API Key for LangGraph agent | |
| TAVILY_API_KEY | Yes | Tavily API Key for web search functionality | |
| LANGCHAIN_API_KEY | No | LangChain API Key for LangSmith tracing/monitoring (optional) | |
| UNSPLASH_ACCESS_KEY | No | Unsplash API Key for high-quality images (optional, falls back to Lorem Picsum) |
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 |
|---|---|
| web_searchC | Search the web for information about the given query |
| roll_diceC | Roll the dice with the given notation |
| create_social_postB | Generate a social media post with image and text for any topic |
| get_slide_imageC | Get presentation-ready images for slides and presentations |
| create_quote_cardC | Generate a quote card with inspirational text and background image |
| github_search_repositoriesB | Search for GitHub repositories by query (e.g., 'python machine learning', 'user:microsoft') |
| github_get_repository_infoC | Get detailed information about a specific GitHub repository |
| github_get_file_contentB | Get the content of a specific file from a GitHub repository |
| github_list_filesB | List files and directories in a GitHub repository path |
| github_auth_statusA | Check GitHub authentication status and rate limits |
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 10 tools
Each tool targets a distinct purpose: web search, dice rolling, social post creation, slide image generation, quote card creation, and five distinct GitHub operations (search, repo info, file content, file listing, auth status). No two tools have overlapping functionality, and the GitHub prefix clearly separates those tools from the general utilities.
All tools use lowercase snake_case with a clear verb_noun pattern (e.g., web_search, roll_dice, create_social_post) and GitHub tools consistently use a github_ prefix followed by a verb_noun structure (e.g., github_search_repositories, github_get_file_content). The naming is highly predictable and conventional.
With 10 tools, the server sits comfortably in the ideal 3-15 range. Each tool contributes a unique capability, and the mix of 5 general content/search utilities and 5 GitHub utilities feels reasonably scoped for a multi-purpose server.
The GitHub toolset covers read-only operations and search, but lacks common write operations such as creating issues or pull requests, making it incomplete for full repository management. The general tools are a mixed bag without a coherent domain, leaving obvious gaps (e.g., no generic image generation beyond slides/quote cards). However, the existing tools do cover their immediate stated purposes.