tinystruct

tinystruct MCP is a Java-based MCP server that exposes a set of built-in tools for filesystem operations and GitHub interactions. It is modular and extensible, built with Maven and organized into submodules for GitHub operations and local filesystem management. You can start the server via the provided dispatcher script, then interact with the server’s tools using the standardized JSON-based communication model provided by TinyStruct. The server ships with ready-to-use tools such as filesystem operations (read, write, list, copy, move, delete) and GitHub-related actions (clone, pull, push, status, issues, PRs, actions). To use these tools, you typically dispatch commands that map to MCP tool actions, and the server responds with JSON payloads that conform to the model context protocol used by TinyStruct. The included HTTP server integration enables LLMs or agents to securely perform operations on the local filesystem and GitHub repositories through well-defined actions.

Prerequisites:

• Java 17 or higher
• Maven 3.8+
• Git

Steps:

1. Clone the repository: git clone https://github.com/tinystruct/tinystruct-mcp.git cd tinystruct-mcp

2. Build the project (all submodules): mvn clean install

3. Start the MCP server using the dispatcher script: bin/dispatcher start --import org.tinystruct.system.HttpServer --import org.tinystruct.mcp.GitHub --import org.tinystruct.mcp.FileSystem --server-port 777

Notes:

• The server port can be changed by adjusting the --server-port value.
• The programmatic startup snippet from the README can be adapted to your own Main class if you prefer embedding the server in a Java application.

Tips and considerations:

• The server exposes GitHub and filesystem tools; ensure proper authentication and permissions are configured for Git operations and GitHub API usage.
• When running in production, consider securing the HTTP server and limiting tool access to trusted agents.
• The tools are annotated with @Action and @Argument to enable automatic schema generation; you can extend by adding new MCPTool classes following the examples in the README.
• If you modify submodules (filesystem or github), rebuild with Maven to ensure the dispatcher has the latest classes.
• The server port can be adjusted as needed; be sure to configure any reverse proxies or firewall rules accordingly.