Priyonuj MCP

MCPAI代理

提供方 未标注

AI代理 stdio · 本地进程 OAuth 授权 社区 / 第三方
查看接入方式

全面解析MCP File NavigatorMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP File Navigator能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

Priyonuj MCP 属于AI代理类 MCP 服务器,stdio · 本地进程,OAuth 授权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
npm install express fs-extra shelljs

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Priyonuj MCP当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Node.js本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.5 KB
来自项目仓库与上游目录的原文,未做删改

MCP File Server

A secure file server implementation using the Model Context Protocol (MCP) that provides a standardized interface for file system operations.

Overview

MCP File Server is a Node.js application that implements an MCP server specifically for file operations. It provides a secure and standardized way to interact with the file system through the MCP protocol, suitable for integration with AI assistants like Claude and developer tools like Cursor.

The server offers the following tools:

File Operations

  • list_files: Lists files in a specified directory
  • read_file: Reads the content of a file
  • write_file: Writes content to a file
  • delete_file: Deletes a file or directory
  • set_base_directory: Sets the base directory for file operations directly from chat
  • get_base_directory: Gets the current base directory

Git Operations

  • git_command: Executes git commands in the base directory

Project Structure

The project follows a modular architecture with services organized by responsibility:```
mcp-file-server/
├── services/ # Service modules
│ ├── configService.js # Configuration management
│ ├── fileService.js # File system operations
│ ├── gitService.js # Git operations
│ ├── loggerService.js # Logging functionality
│ └── toolService.js # MCP tool registration
├── files/ # Default storage directory
├── log/ # Log files
├── examples/ # Example scripts and usage demos
├── mcp_server.js # Main application entry point
├── package.json # Project metadata and dependencies
└── README.md # Documentation


## Security Features

- Robust path validation to prevent directory traversal attacks
- Careful normalization and resolution of file paths
- Command validation to prevent command injection
- Operations logged to a dedicated log file for auditability
- Secure handling of relative paths

## Prerequisites

- Node.js >= 16.0.0
- npm or yarn package manager
- Git (for git_command functionality)

## Installation

1. Clone this repository:```
   git clone <repository-url>
   cd mcp-file-server
   ```

2. Install dependencies:```
   npm install
   ```

## Configuration

### Environment Variables

- `BASE_DIRECTORY`: (Optional) Path to the base directory for file operations. If not specified, defaults to the `files` directory in the project root.

### Directory Structure

- `/files`: Default base directory for file operations
- `/log`: Contains the debug log file

## Usage

### Starting the Server```
npm start

For development with auto-reload:```
npm run dev


The server will run and connect to standard input/output for communication.

### Setting Base Directory from Chat

One of the key features of this implementation is the ability to set the base directory directly from the chat interface. This means you don't need to restart the server or modify configuration files to change where files are stored and accessed.

Simply ask the AI assistant to set the base directory, for example:
- "Set the base directory to C:/Users/username/Documents"
- "Change the file storage location to /home/user/data"

The assistant will use the `set_base_directory` tool to update the location. You can verify the current location at any time by asking for the current base directory.

### Using Git Commands

The server allows you to execute Git commands directly from the chat interface. Simply ask the AI assistant to run a git command, for example:
- "Run git status"
- "Execute git log --oneline"
- "Create a new branch with git checkout -b feature/new-feature"

You can also specify which shell to use:
- "Using PowerShell, run git status"
- "In bash, execute git diff"
- "With cmd, run git pull origin main"

### Configuration Object Example

Below is an example configuration object for integrating the MCP File Server with Claude Desktop or Cursor:```json
{
  "mcpServers": {
    "file-server": {
      "command": "node",
      "args": ["/path/to/mcp-file-server/mcp_server.js"],
      "disabled": false,
      "autoApprove": ["list_files", "read_file", "write_file", "delete_file", "set_base_directory", "get_base_directory", "git_command"]
    }
  }
}

Explanation of configuration properties:

  • mcpServers: Container for all MCP server configurations
  • file-server: A unique identifier for this particular MCP server
  • command: The command to execute (in this case, node to run the JavaScript file)
  • args: Array of arguments to pass to the command (the path to your server script)
  • disabled: Whether this server is currently disabled (false = enabled)
  • autoApprove: List of tools that should be auto-approved without requiring user confirmation

Extending the Server

The modular architecture makes it easy to extend the server with new functionality:

  1. Create a new service in the services/ directory
  2. Add your service's registration to the toolService.js file
  3. Update the main mcp_server.js file to initialize your service

For example, to add a new compression service:
- Create services/compressionService.js
- Add a registerCompressionTools() method to toolService.js
- Update the main server to initialize your compression service

API Reference

set_base_directory

Sets a new base directory for file operations.

Parameters:
- path: The absolute path to the new base directory

Returns:
- Confirmation message

get_base_directory

Gets the current base directory path.

Parameters:
- None

Returns:
- The current base directory path

list_files

Lists files in a specified directory.

Parameters:
- directory: (Optional) Directory path to list (defaults to root)

Returns:
- A formatted list of files and directories

read_file

Reads the content of a file.

Parameters:
- path: Path to the file to read

Returns:
- The content of the file

write_file

Writes content to a file.

Parameters:
- path: Path to the file to write
- content: Content to write to the file

Returns:
- Confirmation message

delete_file

Deletes a file or directory.

Parameters:
- path: Path to the file or directory to delete

Returns:
- Confirmation message

git_command

Executes a git command in the base directory.

Parameters:
- command: Git command to execute (without the 'git' prefix)
- shell: (Optional) Shell to use for execution (cmd, powershell, bash)

Returns:
- Command output (stdout and stderr)

Troubleshooting

Check the log file at log/mcp_debug.log for detailed information about server operations and any errors that might occur.

Common issues:

  1. Path Access Errors: Ensure the BASE_DIRECTORY is set to a location that the process has permission to access.
  2. Connection Refused: Make sure the server is running before attempting to connect.
  3. Tool Not Found: Verify that the tool names in your configuration match exactly with those defined in the server.
  4. Port Conflicts: If you're running multiple MCP servers, ensure they're using different ports.
  5. Invalid Base Directory: When setting a base directory from chat, ensure you provide an absolute path (not relative).
  6. Git Command Errors: Ensure Git is installed and the base directory is a valid Git repository when using git commands.

Contributing

We welcome contributions to improve the MCP File Server! Here's how you can help:

Ways to Contribute

  • Bug Reports: Submit detailed bug reports with steps to reproduce
  • Feature Requests: Suggest new features or improvements
  • Documentation: Help improve or extend the documentation
  • Code Contributions: Submit pull requests with bug fixes or new features

Development Process

  1. Fork the Repository: Create your own fork of the project
  2. Create a Branch: Make your changes in a new branch
  3. Follow Coding Standards: Maintain the existing code style
  4. Write Tests: Add tests for new features or bug fixes
  5. Documentation: Update documentation to reflect your changes
  6. Submit a Pull Request: Open a PR with a clear description of the changes

Pull Request Guidelines

  • Keep PRs focused on a single feature or bug fix
  • Include a clear description of what the changes do and why
  • Make sure all tests pass
  • Update relevant documentation

Reporting Issues

When reporting issues, please include:
- A clear description of the problem
- Steps to reproduce the issue
- Expected behavior vs. actual behavior
- Environment details (OS, Node.js version, etc.)

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Priyonuj MCP 怎么安装?

在客户端按下面的安装命令接入:npm install express fs-extra shelljs。装完在客户端配置里引用同一个包或端点。

Priyonuj MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Priyonuj MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Priyonuj MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Priyonuj MCP 能提供哪些能力?

资料显示能力标签包括 JavaScript、Git集成、OAuth认证。具体工具清单以官方文档为准。

Priyonuj MCP 需要什么运行环境?

运行时为 Node.js;属于本地进程,需要在本机装好运行环境。

Priyonuj MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。