Project Content Server
# Project Content Server
An MCP server that provides access to project files and their contents.
<a href="https://glama.ai/mcp/servers/qmqbqlz2c4"><img width="380" height="200" src="https://glama.ai/mcp/servers/qmqbqlz2c4/badge" alt="Project Content Server MCP server" /></a>
## Installation
1. Clone the repository
2. Install dependencies:
```bash
npm install
```
3. Build the project:
```bash
npm run build
```
## Usage
Start the server:
```bash
node build/index.js
```
### API
#### latest_project_data
Get all files and their contents from a project directory.
**Parameters:**
- `projectPath` (string): Path to the project directory
**Example Request:**
```json
{
"name": "latest_project_data",
"arguments": {
"projectPath": "/path/to/project"
}
}
```
**Example Response:**
```json
{
"file1.txt": "Contents of file1",
"subdir/file2.js": "Contents of file2"
}
```
## Configuration
The server can be configured using environment variables:
- `PORT`: Port to run the server on (default: stdio)
## Error Handling
The server returns errors in the following format:
```json
{
"content": [{
"type": "text",
"text": "Error message"
}],
"isError": true
}
```
Common errors include:
- Invalid project path
- Permission denied errors
- File system errors
## License
MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'latest_project_data' has a clear and distinct purpose of retrieving project data, so disambiguation is perfect.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'latest_project_data' follows a clear verb_noun pattern (get is implied in the description), and there are no other tools to cause inconsistency.
A single tool is generally too few for a server named 'Project Content Server', which suggests a scope that might include operations like creating, updating, or deleting project data. This minimal set feels thin and incomplete for the implied domain.
The server's name implies handling project content, but the tool only provides read access to latest data. There are significant gaps, such as no ability to create, update, delete, or manage project files, which will likely cause agent failures in typical workflows.