Expo MCP Server
# File MCP
A Model Context Protocol (MCP) server that provides file system operations through a standardized API.
Mainly just doing this so I can prototype and integrate error logs into mcp clients.
## Usage
### CLI
```bash
npm run build
npm start
```
### Development
```bash
npm run dev
```
### Testing
```bash
npm run inspect
```
### Available Tools
| Tool Name | Description |
| ----------- | --------------------------------------- |
| `readFile` | Read contents of a file |
| `writeFile` | Write content to a file |
| `listFiles` | List files in a directory |
| `tailFile` | Read the last N lines from a file |
| `listTools` | List all tools registered in the server |
## Installation
```bash
npm install
```
## Build
```bash
npm run build
```
## License
MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: listFiles lists directory contents, listTools lists server tools, readFile reads entire files, tailFile reads file tails, and writeFile writes files. An agent can easily distinguish between these operations.
All tool names follow a consistent verbNoun pattern in camelCase (e.g., listFiles, readFile, writeFile). The naming is predictable and uniform across all five tools.
With 5 tools, this server is well-scoped for basic file operations. Each tool serves a clear and necessary function, making the count appropriate for the domain without being too sparse or bloated.
The toolset covers core file operations (list, read, write) but has notable gaps for a file management domain, such as no deleteFile, moveFile, or createDirectory tools. This limits agent workflows, though basic tasks are supported.