MCP.so
Sign In

MCP Server (Go)

@pyljain

Basic information

Category

Other

Transports

stdio

Author

pyljain

About MCP Server

No overview available yet

#mcp-server#json-rpc#database-querying

MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Server (Go)?

A Go implementation of a Model Context Protocol (MCP) server that provides database querying capabilities through a JSON-RPC interface, integrating with SQLite and supporting Server-Sent Events for real‑time communication.

How to use MCP Server (Go)?

Clone the repository, run go mod download to install dependencies, then execute go run main.go to start the server on port 8777. All requests must include an Authorization header with the token "abcd". Use the / endpoint (GET) to establish an SSE connection and /messages/{sessionID} (POST) to send JSON‑RPC requests for tools like query, tools/list, and tools/call.

Key features of MCP Server (Go)

  • JSON‑RPC 2.0 protocol implementation
  • Server‑Sent Events (SSE) for real‑time communication
  • SQLite database integration
  • Tool‑based architecture for extensible functionality
  • Token‑based authentication support (hardcoded token “abcd”)

Use cases of MCP Server (Go)

  • Execute SQL queries against a SQLite database via JSON‑RPC
  • List all available tables in the database
  • Integrate with AI agents or chatbots that follow the Model Context Protocol

Frequently asked questions

1

What runtime or dependencies are required?

Go 1.x and SQLite3 are required.

2

Where does the database file live?

The server uses an SQLite database file named `mcp.db` located in the project root.

3

How is authentication handled?

The server uses a simple token‑based system with a hardcoded token “abcd”. All requests must include an `Authorization: Bearer <token>` header.

4

What transport does the server use?

It uses a combination of Server‑Sent Events (SSE) for streaming and HTTP POST for JSON‑RPC requests.

5

Are there any known limits?

The README does not mention any specific limits.

Comments

More Other MCP servers