MetaAPP MCP Server
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., "@MetaAPP MCP Server initialize a new MetaApp project called MyApp"
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.
MetaAPP MCP Server
A comprehensive MCP (Model Context Protocol) service for MetaAPP development, providing tools for project initialization, protocol exploration, and blockchain interaction.
Features
Project Management: Initialize, preview, and build MetaApp projects from templates
Environment Detection: Check and guide Node.js and Git installation
Protocol Tools: Query and search MetaID protocols on blockchain
Documentation Access: Built-in MetaID and Metalet wallet API documentation
PIN Management: Fetch and analyze PIN data from blockchain
User Information: Query user profiles by address or MetaID
Prompt Templates: Pre-configured prompts for common MetaApp development tasks
Related MCP server: aptos-mcp
Installation
Prerequisites
Node.js v20.19.1 or higher (recommended via NVM)
npm or yarn
Git
Install Dependencies
npm installDevelopment
Run in Development Mode
npm run devBuild the Project
npm run buildRun Built Version
npm startProcess Management (PM2)
The server includes PM2 configuration for production deployment with auto-restart capabilities.
Start with PM2
npm run pm2:startStop PM2 Process
npm run pm2:stopRestart PM2 Process
npm run pm2:restartView Logs
npm run pm2:logsDocker Deployment
Build Docker Image
npm run docker:build
# or
docker build -t metaapp-mcp-server .Run Docker Container
npm run docker:run
# or
docker run -p 3000:3000 metaapp-mcp-serverMCP Tools
System Tools
get_assistant_metadata: Get complete server metadata including version and features
Documentation Tools
get_resource_tree: MetaID and Metalet wallet API documentation
get_manv1_api_resource: MAN V1 API capabilities and endpoints
get_manv2_api_resource: MAN V2 API capabilities and endpoints
Environment Tools
check_environment: Check if Node.js and Git are installed
install_node_guide: Installation guide for Node.js via NVM
install_git_guide: Installation guide for Git
Project Tools
init_project: Initialize a new MetaApp project from template
Parameters:
project_name,project_description,target_directory
run_project: Run npm run dev to preview the project
Parameters:
project_path
build_project: Build and package the project for deployment
Parameters:
project_path
Protocol Tools
get_metaprotocol_list: Get list of MetaProtocols
Parameters:
cursor(optional),size(optional)
search_protocol: Search for a specific protocol by name
Parameters:
protocol_name
get_pin_detail: Get details of a specific PIN
Parameters:
pin_id
get_pin_list_by_path: Get PIN list by protocol path
Parameters:
path,cursor(optional),size(optional)
get_user_info: Get user information
Parameters:
address_or_metaid
MCP Prompts
Available Prompts
meta_app_developer_guide: Activate professional MetaApp developer mode
init_metaapp_project: Initialize a new MetaApp project
Arguments:
project_name,project_description
explore_protocol: Explore and understand a MetaID protocol
Arguments:
protocol_name
deploy_metaapp: Deploy a MetaApp to the blockchain
Usage Example
With Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"metaapp": {
"command": "node",
"args": ["/path/to/MetaAPP-Mcp/dist/index.js"]
}
}
}Direct Usage
The server runs on stdio transport and communicates via standard input/output:
node dist/index.jsProject Structure
MetaAPP-Mcp/
├── src/
│ ├── config/ # Configuration files
│ ├── prompts/ # Prompt templates
│ ├── tools/ # Tool implementations
│ │ ├── system-tools.ts
│ │ ├── documentation-tools.ts
│ │ ├── project-tools.ts
│ │ └── protocol-tools.ts
│ ├── types/ # TypeScript type definitions
│ ├── utils/ # Utility functions
│ │ ├── helpers.ts
│ │ └── api-client.ts
│ └── index.ts # Main server entry
├── dist/ # Compiled JavaScript
├── logs/ # PM2 logs
├── Dockerfile # Docker configuration
├── ecosystem.config.cjs # PM2 configuration
├── tsconfig.json # TypeScript configuration
└── package.json # Project metadata
API Endpoints
MetaID APIs
MAN V1:
https://man.metaid.io/apiMAN V2:
https://manapi.metaid.io
Key Resources
MetaID Docs: https://docs.metaid.io/
MetaID SDK: https://github.com/metaid-developers/metaid-sdk
MetaApp Template: https://github.com/metaid-developers/MetaApp-CLI
Metalet Wallet: https://metalet.space/
Deployment: https://metaweb-world.vercel.app
Development Workflow
Creating a New MetaApp
Check Environment:
Use: check_environmentInitialize Project:
Use: init_project Parameters: { target_directory: "/path/to/projects" }Explore Protocols:
Use: search_protocol Parameters: { protocol_name: "simplenote" }Develop Features: Follow the protocol structure to implement your app
Build for Deployment:
Use: build_project Parameters: { project_path: "/path/to/project" }Deploy: Upload the generated zip file to https://metaweb-world.vercel.app
Troubleshooting
Node.js Not Found
Use the install_node_guide tool to get installation instructions for your platform.
Git Not Found
Use the install_git_guide tool to get installation instructions for your platform.
Build Errors
Ensure you're in the correct project directory and all dependencies are installed:
cd your-project
npm install
npm run buildContributing
Contributions are welcome! Please follow these guidelines:
Fork the repository
Create a feature branch
Make your changes
Submit a pull request
License
MIT License - see LICENSE file for details
Support
GitHub Issues: Create an issue
MetaID Community: https://metaid.io/
Documentation: https://docs.metaid.io/
Credits
Built with:
MetaAPP MCP Server - Empowering MetaApp development with AI assistance
Available Tools
15 toolsbuild_projectC
Build and package the project for deployment
Inputs: project_path (required).
check_environmentA
Check if Node.js and Git are installed on the system
Inputs: no named parameters.
get_assistant_metadataA
Get complete MetaAPP MCP Server metadata including version, features, and configuration
Inputs: no named parameters.
get_manv1_api_resourceA
Get MAN V1 API capabilities and endpoints
Inputs: no named parameters.
get_manv2_api_resourceB
Get MAN V2 API capabilities and endpoints
Inputs: no named parameters.
get_metaprotocol_listC
Get list of MetaProtocols from /protocols/metaprotocol path
Inputs: size, cursor.
get_pin_detailA
Get details of a specific PIN by its ID
Inputs: pin_id (required).
get_pin_list_by_pathB
Get PIN list by specific path
Inputs: path (required), size, cursor.
get_resource_treeB
Get MetaID and Metalet wallet API documentation and resources
Inputs: no named parameters.
get_user_infoB
Get user information by address or metaid
Inputs: address_or_metaid (required).
init_projectB
Initialize a new MetaApp project from template
Inputs: target_directory (required), project_name, project_description.
install_git_guideB
Get installation guide for Git
Inputs: no named parameters.
install_node_guideA
Get installation guide for Node.js via NVM
Inputs: no named parameters.
run_projectC
Run npm run dev to preview the project
Inputs: project_path (required).
search_protocolB
Search for a specific protocol by name
Inputs: protocol_name (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
MCP server for Klever blockchain smart contract development.
MCP server with quote and live cryptocurrency price tools, local and cloud-deployed transports.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.67 npm155Apache 2.0
- AlicenseBqualityCmaintenanceA MCP server for interacting with Aptos documentation and creating full-stack Aptos blockchain applications.61MIT
- AlicenseAqualityDmaintenanceA meta-MCP server that helps users create new MCP servers through AI guidance, templates, and streamlined workflows, transforming ideas into production-ready implementations with minimal effort.42MIT
- AlicenseNot gradedqualityDmaintenanceA Meta MCP Server that provides persistent memory and intelligent guidance for MCP development projects.-