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
Setup to build and run with Claude
Download and install Claude desktop app from claude.ai/download
Clone the repo, install dependencies and build:
npm install
npm run buildConfigure 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.jsonThis 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.
Restart Claude Desktop.
Look for the hammer icon with the number of available tools in Claude's interface to confirm the server is running.
If this is all working, you should be able to develop your MCP server using
npm run devand 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 inspectTo build on file changes run:
npm run watchOr run both the watcher and inspector:
npm run devPublishing
Once you're ready to distribute your server, it's simple!
Set up an NPM account.
Run
npm publish. This will publish a package using the project name inpackage.jsonOnce 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:
Define the tool schema in
index.tsAdd it to the tools array in the
ListToolsRequestSchemahandlerAdd the implementation in the
CallToolRequestSchemahandler
See the hello_tool implementation as an example.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/MatthewDailey/mcp-starter'
If you have feedback or need assistance with the MCP directory API, please join our Discord server