Skip to main content
Glama
enesjakozh
MaheshDoiphode

Project Content Server

by MaheshDoiphode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

项目内容服务器

提供对项目文件及其内容的访问的 MCP 服务器。

安装

  1. 克隆存储库

  2. 安装依赖项：

    npm install

  3. 构建项目：

    npm run build

Related MCP server: File Tools MCP Server

用法

启动服务器：

node build/index.js

API

最新项目数据

从项目目录中获取所有文件及其内容。

参数：

  • projectPath （字符串）：项目目录的路径

示例请求：

{
  "name": "latest_project_data",
  "arguments": {
    "projectPath": "/path/to/project"
  }
}

响应示例：

{
  "file1.txt": "Contents of file1",
  "subdir/file2.js": "Contents of file2"
}

配置

可以使用环境变量来配置服务器：

  • PORT ：运行服务器的端口（默认值：stdio）

错误处理

服务器返回以下格式的错误：

{
  "content": [{
    "type": "text",
    "text": "Error message"
  }],
  "isError": true
}

常见错误包括：

  • 项目路径无效

  • 权限被拒绝错误

  • 文件系统错误

执照

麻省理工学院

Available Tools

1 tool
latest_project_dataC

Get latest project data including file names and contents

ParametersJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the project directory

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions retrieving 'latest project data' but doesn't specify whether this is a read-only operation, potential side effects, performance characteristics, or error conditions. The description is insufficient for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that communicates the core functionality without unnecessary words. It's appropriately sized for a simple tool, though it could be slightly more structured by separating purpose from scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with good schema coverage but no annotations and no output schema, the description provides basic purpose but lacks important behavioral context. It's minimally adequate but leaves significant gaps in understanding how the tool behaves and what it returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with the single parameter 'projectPath' well-documented in the schema. The description doesn't add any meaningful parameter semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Get') and resource ('latest project data'), specifying it includes 'file names and contents'. This provides a specific verb+resource combination, though without sibling tools, differentiation cannot be evaluated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It simply states what the tool does without indicating appropriate usage scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • First observedlatest_project_data
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • File Tools MCP Server

    BumpyClock
    A
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides file and directory tools for LLMs, including project structure analysis, file reading, and project context resources, with support for .gitignore patterns.
    MIT

  • My MCP Server

    Furkan-Keser
    A
    license
    B
    quality
    A
    maintenance
    A secure file management MCP server enabling file operations like listing, reading, creating, renaming, moving, copying, deleting, and searching within a restricted workspace.
    10
    MIT

Appeared in Searches