How to use MCP Reference Servers

The official reference implementations for filesystem, git, database, and browser MCP servers.

You want to give Claude access to your filesystem, a database, or a browser, but you don't know where to start building an MCP server.

L4L5

Before you startNode.js 18+ or Python 3.10+ • Claude Code with MCP support

Steps

Browse the server catalog and pick one that matches your need

The repo contains reference servers for: filesystem (read/write), git (repo operations), SQLite, PostgreSQL, Puppeteer browser, and more. Pick the closest match and read its README before building anything custom.

Add the server to your Claude Code MCP config

Each server has a configuration snippet for .claude/settings.json or your MCP config file. Add it, restart Claude Code, and verify the tool appears in your session.

I've added the [SERVER_NAME] MCP server to my Claude Code config. What tools should now be available from it? List them and demonstrate one with a simple test call.

[SERVER_NAME]MCP server name e.g. filesystem

Use the reference server as the base for custom extensions

The reference servers are designed to be forked and extended. Once you understand one, you have the pattern for building your own domain-specific MCP server.

How do you know it worked?

At least one reference server installed and showing tools in Claude Code
You've used a server tool in a real session and it returned correct results

If something looks off

Scope file access

File system MCP gives broad access, scope it to specific directories in the config, not your entire home folder.

Don't install all at once

Each server adds tool overhead to every session, install only what you actively use.