mcp

This MCP server bundle exposes three tools you can run through the same MCP interface. text2sql converts natural language prompts into SQL queries by querying your database through the configured JDBC/ODBC connection provided in the link environment variable. dify_retriever accesses a DIFY-backed knowledge base for retrieval and knowledge search, using the given DIFY API key, endpoint, dataset ID, and dataset name. data_transfer provides a general data transformation workflow via the dt tool, enabling lightweight data format or schema conversions. To use these tools, start your MCP server with the provided configuration and call the respective commands (text2sql, dify, dt) from the MCP client or interface, supplying any required environment variables as configured. Each tool runs in stdio mode, so input prompts and outputs flow through standard input/output channels in the MCP session.

Prerequisites:

• Go installed (go1.x or newer) and GOPATH configured, with GOPROXY if needed.
• Internet access to fetch modules and install binaries.

Install each tool locally:

1. text2sql go install github.com/wangle201210/mcp-server/cmd/text2sql@latest

2. dify retriever go install github.com/wangle201210/mcp-server/cmd/dify@latest

3. data transfer utility go install github.com/wangle201210/mcp-server/cmd/dt@latest

Prepare configuration:

• Create a configuration file containing the mcp_config object shown in this document (or adapt to your environment).
• Ensure environment variables required by each tool are set in the config (or supplied by your runtime environment).

Run the MCP server (example):

• Build or run your MCP server binary using the configuration file. Depending on your MCP server implementation, you might run something like:

Assuming a binary named mcp-server: mcp-server --config path/to/your/config.json

Verify: Connect to the MCP server and invoke the available commands (text2sql, dify_retriever, data_transfer) via the MCP interface.

Tips and notes:

• The text2sql tool expects a database connection string in the env.link field. Ensure the database is reachable from the MCP server host and that credentials are correct.
• dify_retriever requires valid DIFY credentials and dataset information. Keep DIFY_ENDPOINT, DIFY_DATASET_ID, and DIFY_DATASET_NAME accurate for successful retrievals.
• data_transfer currently has an empty env block; you can extend it with necessary transformation parameters if your workflow requires them.
• All tools run in stdio mode within the MCP context; inputs and outputs should be provided through the MCP session interface.
• If you encounter permission or path issues, ensure the Go binaries installed with go install are in your PATH.
• For production, consider securing environment variables and restricting access to the MCP interface.