mcp-cline-project-content

This MCP server provides access to project files and their contents. After starting the server, you can use its built-in API (for example, the latest_project_data endpoint) to retrieve all files and their contents from a specified project directory. Start the server with the compiled entry point and then issue a JSON-RPC style request for the latest_project_data method, supplying the projectPath you want to inspect. The server responds with a JSON map of relative file paths to their contents.

To start locally, ensure the build artifacts exist and run the server with Node.js. Example: Call the server’s latest_project_data function by sending a request containing {"name": "latest_project_data", "arguments": {"projectPath": "/path/to/project"}}. The response will be a JSON object mapping filenames to their contents, e.g. {"file1.txt": "Contents of file1", "subdir/file2.js": "Contents of file2"}.

Prerequisites:

• Node.js installed (version compatible with the project)
• npm or yarn

Installation steps:

1. Clone the repository git clone https://github.com/your-org/mcp-cline-project-content-server.git cd mcp-cline-project-content-server

2. Install dependencies npm install

3. Build the project npm run build

4. Run the server node build/index.js

Optional debugging or development steps:

• If you need to run with a specific port, set PORT before starting, e.g. PORT=3000 node build/index.js
• To rebuild after changes, run npm run build again.

Notes and tips:

• The server exposes an API to fetch project file data via latest_project_data; ensure the provided projectPath exists and is accessible by the running process.
• Environment variable PORT can configure the listening port; if not set, the server may default to stdio or a configured default in the code.
• Handle large projects with care; the response can be large as it returns file contents. Consider using a targeted projectPath to limit data.
• Common issues include invalid project paths, permission errors, or filesystem I/O errors. The error format follows a standard structure described in the README: {"content": [{"type": "text", "text": "Error message"}], "isError": true}.