This MCP server exposes the Tsurugi database tools over the Model Context Protocol, enabling you to list tables, fetch metadata, run queries, and perform updates and DDL against a running Tsurugi instance. You can use the provided prompts and tool endpoints (listTableNames, getTableMetadata, query, update, executeDdl) to interact with tsurugi’s data catalog and execute SQL statements. To connect, configure the mcpServers section in your MCP client (e.g., Claude Desktop) to point at the Java-based tsurugi-mcp-server-all.jar, supply the connection URL to your Tsuguri endpoint, and provide credentials as needed. Once connected, you can browse tables, fetch schemas, and execute both read and write operations through the MCP API, with support for transactions (OCC and LTX) and optional write-preserve behavior for multi-file/large operations.

Prerequisites:

• Java 21 or later installed and available on PATH
• Git and a Java build tool if you plan to build locally (optional; the README uses a prebuilt jar)
• Access to a running Tsurugi instance (tsurugidb) compatible with the MCP server

Installation steps:

1. Download or obtain the tsurugi-mcp-server jar (tsurugi-mcp-server-all.jar) from the release page or build it locally using Gradle as described in the repository.
2. Ensure Java is available in your PATH. Verify with: java -version
3. If building from source, clone the repo and build: git clone https://github.com/project-tsurugi/tsurugi-mcp-server cd tsurugi-mcp-server ./gradlew shadowJar

   The jar will be available under build/libs/ as tsurugi-mcp-server-all.jar

4. Run the MCP server with the appropriate configuration, for example: java -jar /path/to/tsurugi-mcp-server-all.jar -c tcp://localhost:12345 --credentials /path/to/credential-file
5. Configure your MCP client (e.g., Claude Desktop) to connect using the provided mcpServers configuration and ensure the target Tsuguri endpoint is reachable.

Notes and tips:

• The MCP server requires a running Tsurugi instance (tsurugidb) and may require authentication depending on your setup. If using Claude Desktop, you can limit tools via the --enable-tools option to enforce read-only access (e.g., enabling only listTableNames, getTableMetadata, and query).
• Environment variable TSURUGI_AUTH_TOKEN can be used to supply an auth token for Tsuguri if token-based auth is configured; otherwise, you can rely on credentials file or no-auth if supported by your setup.
• If you encounter connection issues, verify the connection URL (-c or --connection) and the credentials path. Ensure network access between the MCP server container/process and the Tsurugi instance.
• For production deployments, consider running the MCP server behind a reverse proxy or in a secure network with proper TLS/credentials management, and rotate credentials as needed.
• The supported operations include listTableNames, getTableMetadata, query (with optional transaction_type and cursor for pagination), update (with transactional modes OCC and LTX), and executeDdl for DDL operations.