1. Conduid
  2. Developer Tools
  3. Go MCP
MCP server · Developer Tools

Go MCP

collection of go mcp servers

Unclaimed last commit a year ago devtools
41Fair

Scored 5 months ago · breakdown

About Go MCP

Go MCP is an MCP server published by MikeLuu99 in the Developer Tools category: collection of go mcp servers.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/MikeLuu99/go-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Go MCP

Powered by Claude · Grounded in docs

I know everything about Go MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

Go MCP

A collection of Model Context Protocol (MCP) servers implemented in Go for memory management and research paper storage.

MCP Servers

1. Memory MCP Server

A vector-based memory storage system that provides semantic search capabilities.

Features:

  • Add/update memories with unique IDs
  • Semantic search using vector similarity
  • Metadata support for enhanced context
  • Upstash Vector integration

Tools:

  • add-to-memory: Store or update memory content
  • search-memory: Find memories using semantic similarity
  • get-memory: Retrieve specific memory by ID

2. Research Papers MCP Server

A Redis-based system for storing and retrieving research papers with fuzzy matching.

Features:

  • Store research papers with titles and summaries
  • Exact title matching
  • Fuzzy matching with edit distance for approximate searches
  • Redis backend for reliable storage

Tools:

  • set-new-research-paper: Add new research paper
  • get-research-paper: Retrieve paper with fuzzy matching support

Setup

  1. Install dependencies:
go mod tidy
  1. Create a .env file with required environment variables:
# For Memory MCP
VECTOR_DB_URL=your_upstash_vector_url
TOKEN=your_upstash_token

# For Research Papers MCP
REDIS_URL=your_redis_url

Running the Servers

Memory MCP Server

go run cmd/memory-mcp/main.go

Server runs on port 9090

Research Papers MCP Server

go run cmd/research-papers-mcp/main.go

Server runs on port 8080

API Endpoints

Both servers expose SSE (Server-Sent Events) endpoints:

  • SSE Endpoint: /mcp/sse
  • Message Endpoint: /mcp/message

Testing

The project includes comprehensive test suites for both MCP servers located in the test/ directory.

Running Tests

Run all tests:

go test ./test/... -v

Run tests for specific server:

# Memory MCP tests
go test ./test/memory_mcp_test.go -v

# Research Papers MCP tests  
go test ./test/research_papers_mcp_test.go -v

Test Coverage

Memory MCP Server Tests:

  • add-to-memory tool: Storage with/without metadata, error handling
  • search-memory tool: Semantic search functionality, no results scenarios
  • get-memory tool: Memory retrieval by ID, not found scenarios

Research Papers MCP Server Tests:

  • set-new-research-paper tool: Paper storage, error handling
  • get-research-paper tool: Exact matching, fuzzy matching with Levenshtein distance, boundary conditions

Both test suites use mock implementations to avoid external dependencies during testing.

Dependencies

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Go MCP

How do I install Go MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Go MCP safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Go MCP still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.