go-mcp-server-service

Name: go-mcp-server-service
Author: MCP-Mirror

@MCP-Mirror

Repository

About go-mcp-server-service

Mirror of

#go-mcp-server #note-management #json-rpc

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "AndrewDonelson_go-mcp-server-service": {
      "command": "npx",
      "args": [
        "@modelcontextprotocol/inspector",
        "./bin/dev/<platform>/notes-server"
      ]
    }
  }
}

Tools

Adds a new note to the server

Overview

What is go-mcp-server-service?

go-mcp-server-service is a JSON‑RPC 2.0 compliant server that implements the Model Context Protocol (MCP) for note management. It serves as an example and boilerplate that can be modified for custom MCP projects, supporting cross‑platform development with both a command‑line interface and a service component.

How to use go-mcp-server-service?

Build the server with make dev (development) or make release-all (release), then run it via make run-cmd or make run-service. For integration with Claude Desktop, add an entry pointing to the built binary in claude_desktop_config.json. Debugging can be done using the MCP Inspector with npx @modelcontextprotocol/inspector <binary>.

Key features of go-mcp-server-service

JSON‑RPC 2.0 compliant API
Cross‑platform support (Windows, Linux, macOS)
Thread‑safe note management
Development and release build configurations
CLI and service components
Custom note:// URI scheme for resources

Use cases of go-mcp-server-service

As a starting boilerplate for building custom MCP servers
Managing notes via a command‑line interface
Running note storage as a background system service
Demonstrating MCP resource, tool, and prompt implementations
Testing MCP integration with Claude Desktop

FAQ from go-mcp-server-service

What are the system requirements?

Go 1.21 or later, GNU Make (or compatible), and Git for version information.

How do I build the server?

Use make dev for development builds (with debug symbols and race detection) or make release-all for optimized release builds. Binaries are placed in bin/dev/<platform>/ or bin/release/<platform>/.

How do I configure Claude Desktop?

Add a notes-server entry under mcpServers in claude_desktop_config.json, pointing to the built binary (e.g., ./bin/dev/<platform>/notes-server for development or ./bin/release/<platform>/notes-service for release).

How do I debug the server?

Use the MCP Inspector: run npx @modelcontextprotocol/inspector ./bin/dev/<platform>/notes-server. The Inspector provides a URL for the debugging interface.

What error codes are implemented?

Standard JSON‑RPC 2.0 error codes (-32700, -32600, -32601, -32602, -32603) plus custom codes: -32001 (Resource not found) and -32002 (Unsupported operation).