This MCP server collection provides three Go-based MCP servers that operate over standard input/output (stdio). Each server exposes a different data and query capability via the MCP protocol: text2sql translates natural language questions into executable SQL against a database, dify-retriever uses a knowledge-base-driven approach to generate more aligned AI responses, and ai2mysql-mcp-server facilitates SQL execution and data manipulation against a MySQL database. To use them, run the Go-based servers (one per service) and connect to them using an MCP-compatible client. The servers expect an MCP handshake over stdio, receive a request payload, and return a structured response or query results. You can run multiple servers concurrently on different ports or I/O streams depending on your orchestration setup, then route client requests to the appropriate server by type of task (NL2SQL, knowledge retrieval, or SQL operations).

Prerequisites:

• Go 1.20+ installed on your system
• Basic familiarity with running Go programs from source

Step-by-step:

1. Clone the repository containing the MCP server list (or download the sources for each server): git clone https://github.com/thinkinaixyz-mcp-servers/your-repo-name.git

2. Navigate to each server's directory and install dependencies (Go modules will resolve automatically): cd path/to/text2sql go mod tidy

3. Build or run each server: go run ./text2sql/main.go

   or to build a binary:

   go build -o text2sql ./text2sql/main.go

4. Repeat steps 2-3 for the other servers (dify-retriever and ai2mysql-mcp-server).

5. Configure your MCP client to connect to the appropriate stdio IPC streams or configured ports/streams if you adapt the servers to a network transport. Ensure required environment variables (if any) are set before launching.

Notes and tips:

• These servers are Go-based MCP implementations using stdio for communication. If you adapt them to a network transport, you may need to modify the initialization to listen on a socket or port.
• Ensure GO111MODULE is enabled (GO111MODULE=on) to use Go modules reliably.
• If you encounter import or module resolution issues, run go env GOPROXY and ensure you have network access to fetch modules.
• For production usage, consider building binaries and deploying them behind a process manager or container orchestrator, and supply environment variables (e.g., database connection details for ai2mysql-mcp-server) via a secure config store.
• Debugging tip: run with verbose logging in the server code and capture MCP requests/responses to verify correct protocol handling.