DIY

v1.0.0Developer Toolsstable

DIY (Do It Yourself) - MCP (Model Context Protocol)

diymcpai-integration
Share:
38
Stars
0
Downloads
0
Weekly
0/5

What is DIY?

DIY is a Model Context Protocol (MCP) server that allows AI assistants like Claude, Cursor, and VS Code to diy (do it yourself) - mcp (model context protocol)

DIY (Do It Yourself) - MCP (Model Context Protocol)

This server falls under the Developer Tools category on MCPgee, the world's largest MCP server directory with 33,000+ servers.

Features

  • DIY (Do It Yourself) - MCP (Model Context Protocol)

Use Cases

DIY integration with Model Context Protocol.
jherr

Maintainer

LicenseMIT
Languagetypescript
Versionv1.0.0
UpdatedApr 30, 2026
Statushealthy
Maintenanceactive

Works with

ClaudeOpenAIwindowsmacoslinux

Installation

Manual Installation

npx diy

Configuration

Configuration Details

Config File

claude_desktop_config.json

Performance

Response Metrics

Response Time< 200ms
ThroughputMedium

Resource Usage

Memory UsageLow
CPU UsageLow

How to Set Up and Use DIY

The DIY MCP Server is an educational, from-scratch TypeScript implementation of a Model Context Protocol server that demonstrates how to build an MCP server without using any high-level SDK, communicating directly over stdio via JSON-RPC 2.0. It exposes a simple Coffee Shop menu as MCP resources and provides two tools — getDrinkNames and getDrinkInfo — that an MCP client can call to query available drinks and their details. The project is intentionally minimal and was created as a companion to a tutorial on building MCP servers from first principles, making it ideal for developers who want to understand the wire protocol before adopting higher-level abstractions.

Prerequisites

  • Node.js 18 or newer installed
  • pnpm package manager installed (npm install -g pnpm)
  • TypeScript 5.x installed globally or as a dev dependency
  • An MCP-compatible client such as Claude Desktop or the MCP Inspector for testing
  • Basic familiarity with TypeScript and the JSON-RPC 2.0 protocol
1

Clone the repository

Clone the diy-mcp repository from GitHub and navigate into the server directory.

git clone https://github.com/jherr/diy-mcp.git
cd diy-mcp/server
2

Install dependencies

Install the project's dev dependencies (TypeScript and Node types) using pnpm.

pnpm install
3

Build the TypeScript source

Compile the TypeScript source file in src/index.ts to JavaScript in the dist directory.

pnpm build
4

Inspect the server with MCP Inspector

Use the MCP Inspector to interactively test the server's tools and resources before connecting a full client.

npx @modelcontextprotocol/inspector node dist/index.js
5

Add to your MCP client configuration

Register the built server with your MCP client so it can call getDrinkNames and getDrinkInfo tools and access the menu:// resource.

{
  "mcpServers": {
    "diy-coffee-shop": {
      "command": "node",
      "args": ["/absolute/path/to/diy-mcp/server/dist/index.js"]
    }
  }
}

DIY Examples

Client configuration (Claude Desktop)

Add the DIY Coffee Shop MCP server to Claude Desktop. Replace the path with the absolute path to your compiled dist/index.js.

{
  "mcpServers": {
    "diy-coffee-shop": {
      "command": "node",
      "args": ["/absolute/path/to/diy-mcp/server/dist/index.js"]
    }
  }
}

Prompts to try

Test prompts that exercise the getDrinkNames and getDrinkInfo tools exposed by the DIY MCP server.

- "What drinks are available in the coffee shop?"
- "Tell me more about the Flat White — what's in it and how much does it cost?"
- "List all menu items and their prices."
- "Which drink is the most expensive on the menu?"

Troubleshooting DIY

pnpm build fails with TypeScript errors.

Ensure you have TypeScript installed. Run 'pnpm install' first to get the dev dependencies, then retry 'pnpm build'. The tsconfig.json targets ESNext modules, so Node 18+ is required.

MCP client shows 'server not found' or fails to start the server process.

Use the absolute path to dist/index.js in your client configuration, not a relative path. Confirm the file exists by running 'ls /absolute/path/to/diy-mcp/server/dist/index.js' in your terminal.

Tools list is empty when connecting via MCP Inspector.

The server implements a minimal JSON-RPC handler from scratch. Make sure the build succeeded and you are pointing the inspector at 'node dist/index.js' (not the TypeScript source). The compiled output should be in server/dist/index.js.

Frequently Asked Questions about DIY

What is DIY?

DIY is a Model Context Protocol (MCP) server that diy (do it yourself) - mcp (model context protocol) It connects AI assistants to external tools and data sources through a standardized interface.

How do I install DIY?

Follow the installation instructions on the DIY GitHub repository. Clone the repo, install dependencies, and add the server config to your AI client.

Which AI clients work with DIY?

DIY works with all major MCP-compatible AI clients including Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Cline.

Is DIY free to use?

Yes, DIY is open source and available under the MIT license. You can use it freely in both personal and commercial projects.

Browse More Developer Tools MCP Servers

Explore all developer tools servers available in the MCPgee directory. Each server includes setup guides for Claude, Cursor, and VS Code.

Quick Config Preview

{ "mcpServers": { "diy": { "command": "npx", "args": ["-y", "diy"] } } }

Add this to your claude_desktop_config.json or .cursor/mcp.json

Read the full setup guide →

Ready to use DIY?

Browse our complete directory of 33,000+ MCP servers, read setup guides for your editor, and start building with the Model Context Protocol.

33,000+ ServersFree & Open SourceStep-by-Step Guides