Expo Docs 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_expo_docsC | Search through Expo documentation |
| get_expo_doc_contentC | Get the full content of a specific Expo documentation page |
| list_expo_sections | List all available documentation sections and topics |
| get_expo_api_referenceB | Get API reference for a specific Expo SDK module |
| get_expo_quick_startB | Get quick start guide for Expo |
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 4 tools
Each tool has a distinct purpose: searching documentation, retrieving page content, getting API reference, and getting quick start guide. No overlap.
Most tools follow 'get_expo_*' pattern, but 'search_expo_docs' uses 'search_' instead. Still consistent snake_case and clear verb_noun structure.
Four tools is a reasonable number for a documentation-focused server, covering search, content retrieval, API reference, and quick start.
Core documentation needs are covered (search, page content, API reference, quick start). Missing features like listing categories or version-specific search, but these are minor gaps.