go-mcp-server-service

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is go-mcp-server-service?

The go-mcp-server-service is a JSON-RPC 2.0 compliant server that implements the Model Context Protocol (MCP) for managing notes. It serves as a boilerplate for developers to create their own note management systems.

how to use go-mcp-server-service?

To use the go-mcp-server-service, clone the repository from GitHub, build the project using the provided Makefile, and run the command-line interface or service component to manage notes.

key features of go-mcp-server-service?

  • JSON-RPC 2.0 compliant API for seamless integration.
  • Cross-platform support for Windows, Linux, and macOS.
  • Thread-safe note management ensuring data integrity.
  • Custom note:// URI scheme for accessing notes.
  • Command-line interface and service components for flexible usage.

use cases of go-mcp-server-service?

  1. Building a personal note-taking application.
  2. Integrating note management into larger software systems.
  3. Developing educational tools that require note storage and retrieval.

FAQ from go-mcp-server-service?

  • Is go-mcp-server-service suitable for production use?

Yes, it is designed to be robust and can be used in production environments with proper configuration.

  • What programming language is used?

The server is built using Go (Golang).

  • How can I contribute to the project?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago