HTML Maker

Starter template to build MCP servers with tools, resources, and prompts for MCP-compatible AI assistants.

javascript

0

GitHub Stars

javascript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "ricleedo-html-maker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@r-mcp/boilerplate@latest"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY",
        "DATABASE_URL": "YOUR_DATABASE_URL"
      }
    }
  }
}

You can quickly build and run an MCP server that exposes custom tools, resources, and prompts to MCP-compatible AI assistants. This server framework provides a solid foundation, integrates with multiple clients, and can publish updates to npm for easy distribution.

How to use

You will install or run the server via an MCP client. Production clients like Claude Desktop, Cursor, Claude Code, and Gemini can connect to your server using the standard MCP install flow. Once connected, your tools, resources, and prompts become available to AI assistants, enabling dynamic actions and content delivery. Start by installing or running the server through your preferred method, then restart your MCP client to load the new server configuration.

How to install

Prerequisites you need before installation are Node.js (with npm or pnpm) and Git. Ensure you have a working development environment.

Step 1: Install the MCP server package or use the published package directly.

Option A: Use the published package directly without cloning.

Run the server directly with npx

npx @r-mcp/boilerplate

Option B: Customize and develop locally.

Clone the boilerplate repository, install dependencies, build, and start the server.

# Clone the boilerplate
git clone <your-repo-url>
cd mcp-server-boilerplate

# Install dependencies
pnpm install

# Build the project
pnpm run build

# Start the server
pnpm start

Additional sections

Environment variables are supported via a local .env.local file. Create this file to configure API keys, database connections, or other secrets, and these variables will be automatically included in MCP server configurations during installation.

Tools, resources, and prompts are defined in code. You can add new tools by registering them with the server, define resources that return dynamic content, and create reusable prompts for common operations.

Project structure includes dedicated folders for source code, build scripts, and distribution artifacts. A typical setup contains source files for the MCP server, a build script, and a runtime distribution you can publish to npm.

Development workflow includes local development steps to edit source files, build, test locally, and publish updates to npm. After publishing, clients using the latest tag automatically update.

Environment variables example you can place in .env.local:

# .env.local
API_KEY=your-api-key
DATABASE_URL=your-database-url

Available tools

hello-world

A simple tool that returns a greeting using a provided name parameter.

get-mcp-docs

Fetches or compiles MCP documentation content for integration with AI assistants.