Skip to main content
Glama
MCP Starter Server

MCP Starter Server

MCP Starter Server

A minimal ModelContextProtocol server template for building AI assistant tools. This starter provides a basic structure for creating MCP tools that can be used with AI assistants like Claude.

Features

  • Simple "hello world" tool example

  • TypeScript + esbuild setup

  • Development tools preconfigured

Related MCP server: MCP Server Scaffold

Setup to build and run with Claude

  1. Download and install Claude desktop app from claude.ai/download

  2. Clone the repo, install dependencies and build:

npm install
npm run build
  1. Configure Claude to use this MCP server. If this is your first MCP server, in the root of this project run:

echo '{
  "mcpServers": {
    "mcp-starter": {
      "command": "node",
      "args": ["'$PWD'/dist/index.cjs"]
    }
  }
}' > ~/Library/Application\ Support/Claude/claude_desktop_config.json

This should result in an entry in your claude_desktop_config.json like:

"mcpServers": {
  "mcp-starter": {
    "command": "node",
    "args": ["/Users/matt/code/mcp-starter/dist/index.cjs"]
  }
}

If you have existing MCP servers, add the mcp-starter block to your existing config. It's an important detail that the args is the path to <path_to_repo_on_your_machine>/mcp-starter/dist/index.cjs.

  1. Restart Claude Desktop.

  2. Look for the hammer icon with the number of available tools in Claude's interface to confirm the server is running.

  3. If this is all working, you should be able to develop your MCP server using npm run dev and test it in Claude. You'll need to restart Claude each time to restart the MCP server.

Developing with Inspector

For development and debugging purposes, you can use the MCP Inspector tool. The Inspector provides a visual interface for testing and monitoring MCP server interactions.

Visit the Inspector documentation for detailed setup instructions.

To test locally with Inspector:

npm run inspect

To build on file changes run:

npm run watch

Or run both the watcher and inspector:

npm run dev

Publishing

Once you're ready to distribute your server, it's simple!

  1. Set up an NPM account.

  2. Run npm publish. This will publish a package using the project name in package.json

  3. Once published, others can install the server with a config entry like:

"mcpServers": {
  "<your-package-name>": {
    "command": "npx",
    "args": ["<your-package-name>"]
  }
}

Available Tools

The server provides:

  • hello_tool: A simple example tool that takes a name parameter and returns a greeting

Creating New Tools

To add new tools:

  1. Define the tool schema in index.ts

  2. Add it to the tools array in the ListToolsRequestSchema handler

  3. Add the implementation in the CallToolRequestSchema handler

See the hello_tool implementation as an example.

Available Tools

1 tool
hello_toolD

Hello tool

Inputs: name (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    C2.2/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools, making it perfectly clear which tool to use for any task within this server's scope.

    Naming Consistency5/5

    The single tool name 'hello_tool' follows a consistent verb_noun pattern, and with no other tools to compare, there is no inconsistency in naming conventions.

    Tool Count2/5

    One tool is generally too few for a server's purpose unless it is extremely trivial, which 'hello_tool' suggests. This feels thin and under-scoped for a typical MCP server, indicating a mismatch in tool count appropriateness.

    Completeness1/5

    With only a 'hello_tool', the server lacks any meaningful coverage of a domain. It is severely incomplete, as there are no operations for CRUD, lifecycle management, or any substantive workflows, making it inadequate for agent-driven tasks.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A basic starter project for building Model Context Protocol (MCP) servers that enables standardized interactions between AI systems and various data sources through secure, controlled tool implementations.
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A minimal Model Context Protocol server built with FastAPI that provides a basic "Hello World" resource and tool. Serves as a starting point for building and validating MCP client integrations with richer resources and tools.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A bare-bones FastMCP server template designed to serve as a starting point for building custom Model Context Protocol servers. It provides a foundational structure for implementing tools over HTTP and includes a built-in health check utility.
      GPL 3.0