MetaAPP 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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_assistant_metadataA | Get complete MetaAPP MCP Server metadata including version, features, and configuration |
| get_resource_treeB | Get MetaID and Metalet wallet API documentation and resources |
| get_manv1_api_resourceA | Get MAN V1 API capabilities and endpoints |
| get_manv2_api_resourceB | Get MAN V2 API capabilities and endpoints |
| check_environmentA | Check if Node.js and Git are installed on the system |
| install_node_guideA | Get installation guide for Node.js via NVM |
| install_git_guideB | Get installation guide for Git |
| init_projectB | Initialize a new MetaApp project from template |
| run_projectC | Run npm run dev to preview the project |
| build_projectC | Build and package the project for deployment |
| get_metaprotocol_listC | Get list of MetaProtocols from /protocols/metaprotocol path |
| search_protocolB | Search for a specific protocol by name |
| get_pin_detailA | Get details of a specific PIN by its ID |
| get_pin_list_by_pathB | Get PIN list by specific path |
| get_user_infoB | Get user information by address or metaid |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| meta_app_developer_guide | Professional MetaApp developer assistant guide with MCP tool support |
| init_metaapp_project | Initialize a new MetaApp project |
| explore_protocol | Explore and understand a MetaID protocol |
| deploy_metaapp | Deploy a MetaApp to the blockchain |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Most tools have distinct purposes, but there is some overlap between get_resource_tree, get_manv2_api_resource, and get_manv1_api_resource, which all retrieve API documentation. However, descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_assistant_metadata, init_project, search_protocol). No mixing of styles.
With 15 tools, the server covers project setup, environment checks, and API resource discovery without being overwhelming. The count is well-scoped for its purpose.
The tool set covers key aspects of MetaAPP development: project lifecycle, environment setup, and resource access. Minor gaps exist, such as lacking tools for project stopping or testing, but core workflows are supported.