Renderer MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Renderer MCP Server show me how to configure dark mode in Renderer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Renderer MCP Server
AI-powered assistant for the Renderer portfolio framework
Helps users explore documentation, validate configurations, generate templates, and customize their portfolios through natural language.
Features ⢠Installation ⢠Usage ⢠Tools ⢠Configuration
š Features
š Interactive Documentation - Search and explore Renderer docs with natural language queries
ā Configuration Validation - Validate TOML configs with detailed error messages
šØ Template Generation - Generate starter templates customized to your needs
š” Smart Examples - Get configuration examples with explanations
š Feature Discovery - Search for specific Renderer features and capabilities
š Setup Guides - Step-by-step guides for beginners and advanced users
šļø Repository Browser - Browse Renderer repository files and directories
Related MCP server: Gen-PDF MCP Server
š¦ Installation
NPM (Recommended)
npm install -g renderer-mcp-serverFrom Source
git clone https://github.com/NishikantaRay/renderer-mcp-server.git
cd renderer-mcp-server
npm install
npm run build
npm linkš Usage
With Claude Desktop
Install the server:
npm install -g renderer-mcp-serverConfigure Claude Desktop:
Edit your Claude config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Add the server configuration:
{ "mcpServers": { "renderer": { "command": "renderer-mcp", "env": { "GITHUB_TOKEN": "your_github_token_here" } } } }Get a GitHub Token (Optional but recommended):
Create a new token with
reposcopeAdd it to the config above
Restart Claude Desktop
With Other MCP Clients
Any MCP-compatible client can use this server:
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
const client = new Client({
name: "my-client",
version: "1.0.0",
});
// Connect to the server
await client.connect({
command: "renderer-mcp",
env: {
GITHUB_TOKEN: process.env.GITHUB_TOKEN,
},
});š ļø Available Tools
1. explore_renderer_docs
Search and explore Renderer framework documentation.
Query: "How do I configure dark mode?"
Returns: Relevant documentation sections2. get_renderer_file
Get contents of specific files from the Renderer repository.
Path: "config/home.toml"
Returns: File contents with syntax highlighting3. list_renderer_files
List files and directories in the Renderer repository.
Path: "config"
Returns: Directory listing with file types4. validate_toml_config
Validate TOML configuration files.
Config Content: "[profile]\nname = 'John'"
Config Type: "home"
Returns: Validation results with suggestions5. generate_starter_template
Generate customized starter templates.
Input: { name: "John Doe", github: "johndoe", include_projects: true }
Returns: Complete project structure and configs6. get_config_example
Get example configurations with explanations.
Config Type: "projects"
Returns: Annotated example configuration7. search_renderer_features
Search for specific features.
Feature: "analytics"
Returns: Feature documentation and examples8. get_setup_guide
Get setup instructions.
Level: "beginner" | "advanced"
Returns: Step-by-step setup guideš Configuration
Environment Variables
GITHUB_TOKEN (optional): GitHub personal access token for higher API rate limits
Without token: 60 requests/hour
With token: 5000 requests/hour
Scope required:
public_repo
Custom Repository
By default, the server connects to NishikantaRay/renderer. To use a fork or different repository:
Edit src/constants.ts:
export const DEFAULT_CONFIG: RendererConfig = {
owner: "your-username",
repo: "your-repo",
branch: "main"
};š Project Structure
renderer-mcp-server/
āāā src/
ā āāā index.ts # Main server entry point
ā āāā types.ts # TypeScript type definitions
ā āāā constants.ts # Tool definitions and config
ā āāā github.ts # GitHub API interactions
ā āāā tools/ # Tool implementations
ā āāā validator.ts # TOML validation
ā āāā template.ts # Template generation
ā āāā examples.ts # Configuration examples
ā āāā features.ts # Feature search
ā āāā guides.ts # Setup guides
āāā build/ # Compiled JavaScript
āāā package.json
āāā tsconfig.json
āāā README.mdš§ Development
Prerequisites
Node.js 18 or higher
npm or yarn
TypeScript 5.3+
Setup
# Clone the repository
git clone https://github.com/NishikantaRay/renderer-mcp-server.git
cd renderer-mcp-server
# Install dependencies
npm install
# Build
npm run build
# Watch mode (for development)
npm run watchTesting
# Build the project
npm run build
# Test with MCP inspector
npx @modelcontextprotocol/inspector renderer-mcpš Example Interactions
Generate a Portfolio
User: "Create a portfolio template for John Doe with GitHub and LinkedIn"
Server: Generates complete starter template with:
Customized TOML configurations
Project structure
Setup instructions
Next steps
Validate Configuration
User: "Validate this TOML: [profile]\nname = 'Jane'"
Server:
ā Validates syntax
Checks for required fields
Provides suggestions
Shows parsed structure
Explore Features
User: "How do I add dark mode to my portfolio?"
Server: Returns documentation about:
Theme configuration
Available options
Implementation details
Code examples
š¤ Contributing
Contributions are welcome! Please follow these steps:
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-featureMake your changes
Add tests if applicable
Commit:
git commit -m 'Add amazing feature'Push:
git push origin feature/amazing-featureOpen a Pull Request
Development Guidelines
Follow TypeScript best practices
Keep functions small and focused
Add JSDoc comments for public APIs
Update README for new features
Test thoroughly before submitting
š License
MIT License - see LICENSE file for details
š Related Projects
Renderer - The portfolio framework this server supports
Model Context Protocol - The protocol specification
MCP SDK - Official MCP SDK
š¬ Support
Issues: GitHub Issues
Discussions: GitHub Discussions
Renderer Docs: Documentation
š Acknowledgments
Built with Model Context Protocol SDK
Powers the Renderer framework
Inspired by the MCP community
Made with ā¤ļø by Nishikanta Ray
ā Star this repo if you find it helpful!
Available Tools
8 toolsexplore_renderer_docsB
Search and explore Renderer framework documentation. Returns relevant documentation sections based on your query.
Inputs: query (required).
generate_starter_templateB
Generate a complete starter template for a Renderer portfolio with customized configuration.
Inputs: name (required), email, github, twitter, +4 more.
get_config_exampleA
Get example TOML configuration with explanations for a specific section.
Inputs: config_type (required).
get_renderer_fileA
Get the contents of a specific file from the Renderer repository. Useful for viewing examples, configs, or source code.
Inputs: path (required).
get_setup_guideA
Get step-by-step setup instructions for using the Renderer framework.
Inputs: level.
list_renderer_filesB
List files and directories in a specific path of the Renderer repository.
Inputs: path.
search_renderer_featuresB
Search for specific features or capabilities in the Renderer framework.
Inputs: feature (required).
validate_toml_configA
Validate TOML configuration syntax and structure. Checks for common errors and provides suggestions.
Inputs: config_type (required), config_content (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
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.
Maintenance
Related MCP Connectors
An interactive portfolio built for AI conversations. Browse work, services, and book calls.
Render HTML, URLs, and templates to PDF. AI drafts templates and fixes them from logs.
Query portfolio case studies, verified developer tools, and the AI-UI design system.
Build, version and render resumes as PDFs from Claude or any MCP client.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to generate professional documentation using structured templates based on the POWER framework. Provides access to standardized templates for README, architecture, API, components, and schema documentation.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to generate professional PDF documents from markdown content with advanced typography, syntax highlighting, math equations, dark mode, and customizable styling options.MIT
- AlicenseBqualityAmaintenanceProvides comprehensive Terragrunt documentation, configuration generation, and tooling integration for AI assistants, enabling intelligent assistance with Terragrunt configurations, CLI commands, and HCL syntax.87MIT
- AlicenseAqualityDmaintenanceGenerate production-ready PDFs from Markdown, HTML, or built-in templates (invoices, resumes, reports) directly from Claude or any MCP-compatible AI agent via the DocRenders API.616 npmMIT