Expo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| readFileC | Read the contents of a file |
| writeFileC | Write content to a file |
| listFilesC | List files in a directory |
| tailFileB | Read the last N lines from a file |
| listToolsB | List all available tools in this MCP server |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.