Provides tools for managing Expo development servers for React Native applications, including starting, stopping, and monitoring servers, capturing logs, and retrieving log statistics.
Offers file system operations within project directories, allowing reading, writing, and listing files to support development and debugging workflows.
Enables starting Expo development servers specifically for iOS application development and testing.
Supports development workflows for React Native applications built with Expo, enabling file operations and process management for React Native projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Expo MCP Server show me the last 20 lines from the Expo development server logs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
npm run build
npm startnpm run devnpm run inspectTool Name | Description |
| Read contents of a file |
| Write content to a file |
| List files in a directory |
| Read the last N lines from a file |
| List all tools registered in the server |
Related MCP server: Ember MCP Server
npm installnpm run buildMIT
List files in a directory
Inputs: directoryPath (required).
List all available tools in this MCP server
Inputs: no named parameters.
Read the contents of a file
Inputs: filePath (required).
Read the last N lines from a file
Inputs: filePath (required), lines (required).
Write content to a file
Inputs: content (required), filePath (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
Model Context Protocol server for Studex tools, notifications, and profile integrations
