go -file

This MCP server provides a local file system indexing and access service for MCP clients. It uses SQLite to store the file index and exposes two core APIs: a query API to search and browse the indexed files, and a file-open API to retrieve or stream file contents. The server is designed to be operable via a UI for administrative actions and also via MCP clients that connect to the exposed endpoints. The configuration example shows a single MCP server named 'filesystem' exposing a URL at http://localhost:8888/sse, which is used by clients to fetch index data and perform MCP operations. To use it, start the server (for example via Docker) and point your MCP clients to the configured endpoint; the UI can be used for interactive management and index updates, while programmatic MCP calls can be made by clients that understand the standard MCP protocol.

Prerequisites:

• Docker installed on your host (for the recommended Docker deployment).
• Optional: access to a local directory to act as the underlying storage or data mount, depending on how the image is configured.

Installation steps:

1. Pull the Go MCP File Server image (example image from the repository): docker pull linimbus/go-mcp-file-server

2. Run the container, exposing the service on port 8888 and (optionally) mounting a local data directory: docker run -d
   -p 8888:8888
   -v /path/to/data:/data
   --name mcp-file-server
   linimbus/go-mcp-file-server

3. Verify the service is up by curling the server endpoint or visiting http://localhost:8888/sse in a browser/MCP client.

Notes:

• The exact image name and required environment variables (such as port or data paths) may vary; adjust the docker run command to match the image's documentation.
• If you prefer building from source, ensure you have Go installed and follow the repository's build instructions (not provided in this README).

Tips:

• Ensure the port 8888 (or the configured port) is open in your firewall so MCP clients can connect.
• If your MCP client expects a specific endpoint shape (for example /sse for Server-Sent Events), make sure the server is configured to serve that path.
• When using Docker, map a host directory to the container if you want persistent index storage (e.g., -v /path/to/data:/data).
• If you encounter index sync issues, check the container logs and verify that SQLite write permissions are correctly set for the mounted data directory.
• The README shows a minimal config with a single filesystem server; additional MCP servers can be added by expanding the mcpServers map with new keys and endpoints.