BluestoneApps MCP Remote 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 |
|---|---|
| get_project_structureB | Get project structure standards for React Native development |
| get_api_communicationB | Get API communication standards for React Native development |
| get_component_designB | Get component design standards for React Native development |
| get_state_managementB | Get state management standards for React Native development |
| get_component_exampleC | Get a React Native component example |
| get_hook_exampleC | Get a React Native hook example |
| get_service_exampleC | Get a React Native service example |
| get_screen_exampleC | Get a React Native screen example |
| get_theme_exampleB | Get code for a React Native theme |
| list_available_examplesB | List all available code examples by category |
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 10 tools
Most tools have clearly distinct purposes targeting different aspects of React Native development (standards, examples, structure). However, there is some potential overlap between 'get_component_example' and 'get_screen_example' since screens are composed of components, which could cause minor confusion about which to use for component-level examples.
All tools follow a consistent 'verb_noun' pattern using 'get_' or 'list_' prefixes with snake_case naming. The naming convention is perfectly uniform across all 10 tools, making them predictable and easy to understand.
With 10 tools, this server is well-scoped for its purpose of providing React Native development standards and examples. Each tool serves a specific, valuable function, and the count is neither too sparse nor overwhelming for this educational/reference domain.
The tool set provides comprehensive coverage for retrieving standards and examples across key React Native development areas (components, hooks, screens, services, state management, theming, project structure, API communication). A minor gap is the lack of tools for creating or modifying these resources, but as a reference server focused on 'getting' information, it's reasonably complete.