Renderer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for higher API rate limits. Without token: 60 requests/hour, with token: 5000 requests/hour. Scope required: public_repo. |
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 |
|---|---|
| explore_renderer_docsB | Search and explore Renderer framework documentation. Returns relevant documentation sections based on your query. |
| get_renderer_fileA | Get the contents of a specific file from the Renderer repository. Useful for viewing examples, configs, or source code. |
| list_renderer_filesB | List files and directories in a specific path of the Renderer repository. |
| validate_toml_configA | Validate TOML configuration syntax and structure. Checks for common errors and provides suggestions. |
| generate_starter_templateB | Generate a complete starter template for a Renderer portfolio with customized configuration. |
| get_config_exampleA | Get example TOML configuration with explanations for a specific section. |
| search_renderer_featuresB | Search for specific features or capabilities in the Renderer framework. |
| get_setup_guideA | Get step-by-step setup instructions for using the Renderer framework. |
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 8 tools
Most tools are clearly distinct by resource and action, such as listing files versus getting file contents. The main overlap is between explore_renderer_docs and search_renderer_features, which both surface framework information and could be confused.
All tool names use lowercase snake_case and follow a consistent verb_noun pattern, e.g., get_renderer_file, list_renderer_files, validate_toml_config. This makes the set predictable and easy to navigate.
Eight tools is a well-scoped size for a framework documentation and configuration server. Each tool addresses a meaningful task without unnecessary redundancy or bloat.
The tool set covers documentation exploration, file access, config validation, examples, templates, and setup guidance, which addresses the core workflow. A minor gap is that there is no direct tool for rendering or previewing a project, but that may be outside the server's stated purpose.