home / mcp / appsai mcp server
Provides a bridge to external MCP servers, enabling AppsAI projects to access additional tools via standard MCP connections and environment key management.
Configuration
View docs{
"mcpServers": {
"appsai-inc-mcp-server": {
"command": "npx",
"args": [
"-y",
"@appsai/mcp-server"
],
"env": {
"APPSAI_API_KEY": "YOUR_API_KEY"
}
}
}
}You can connect AppsAI projects to external MCP servers to extend tool access, automate workflows, and manage AI-assisted development across frontend, backend, and infrastructure components. This MCP server enables you to run the AppsAI MCP client locally via npm-based execution, securely pass API keys, and register AI agents to access additional capabilities from connected servers.
You use the AppsAI MCP server by wiring it into your AppsAI projects as an external MCP server. Start by adding the MCP server to your project, then configure your client to communicate with it. Once connected, your AI agents can invoke tools exposed by the MCP server to perform actions such as project management, code generation, deployment, and resource orchestration within your AppsAI environment.
Prerequisites you need before installation include Node.js 18 or later and an AppsAI account with credits.
Install steps proceed as follows. Run the commands in order to set up the MCP server for AppsAI projects.
# 1) Ensure Node.js is installed (version 18+). Check with:
node -v
# 2) Install the MCP server globally or run from project context as needed (examples show local usage):
# Claude Code path
claude mcp add appsai -e APPSAI_API_KEY=your_key -- npx -y @appsai/mcp-server
# Claude Desktop configuration (example JSON snippet you can adapt)
# Add to claude_desktop_config.json
{
"mcpServers": {
"appsai": {
"command": "npx",
"args": ["-y", "@appsai/mcp-server"],
"env": {
"APPSAI_API_KEY": "your_key"
}
}
}
}
# Cursor / Windsurf configuration (MCP settings):
# Command: npx -y @appsai/mcp-server
# Environment: APPSAI_API_KEY=your_key
# 3) Install and run locally if you prefer a direct npm-based approach
# This step demonstrates running the MCP server via npx in the project context
npx -y @appsai/mcp-server
# 4) Ensure your API key is set correctly in the environment or as part of the command line
export APPSAI_API_KEY=your_key
# 5) Start or register the server per your project setup as needed by your AppsAI workflowSecurity and credentials: store API keys securely and prefer environment variables over hard-coding keys in commands or configuration files. Use project-scoped or user-scoped credentials as appropriate for your workflow.
Usage notes: you can register multiple MCP servers to a single AppsAI project. Each server may provide a different set of tools or capabilities. You can enable or disable individual MCP servers as your needs evolve.
Troubleshooting tips: ensure that the APPSAI_API_KEY is correctly provided to each MCP client invocation. If your AI agents report missing tools or failed invocations, verify the MCP server is reachable and that the correct server name or label is used in your AppsAI project settings.
The AppsAI MCP integration supports connecting to external MCP servers to extend tool availability for your projects. Use the provided commands to add and configure MCP servers within your AppsAI workflow.
Deploy backend infrastructure for the MCP ecosystem, including services, databases, and supporting resources.
Deploy frontend assets to a CDN or hosting environment, ensuring the user interface is accessible.
Deploy both frontend and backend components of the AppsAI project and MCP integration.
Retrieve deployment status, URLs, and health checks for all connected MCP components.
Obtain deployment artifacts and historical records related to MCP server deployments.
Connect two AppsAI projects to enable cross-app operations and shared tools.
Disconnect two AppsAI projects and remove cross-project tool access.
Add an external MCP server to a project for extended tooling.
List all MCP servers configured for a given AppsAI project.
Update the configuration of an existing MCP server in the project.
Remove an MCP server from the project configuration.
Retrieve your current subscription plan and included credits.
Initiate a subscription purchase flow for the user.
Open the Stripe billing portal for managing payments and plans.
Add credits or funds to your AppsAI account.
Query the current credit balance across your account.
List invoices associated with the account and subscriptions.
List saved payment methods for future charges.
Publish a project template to the marketplace for sharing or sale.
Remove a published template from the marketplace.
Browse available templates in the marketplace.
Get detailed information about a marketplace template.
Fork a marketplace template into your own workspace.
List templates you have published on the marketplace.
View templates you have purchased from the marketplace.
Check if a subdomain is available for a project.
Update the subdomain associated with a project.
Add a custom domain to your project.
Verify DNS configuration for a custom domain.
Remove a custom domain from the project.
List collaborators for the current project.
Invite a new user to join the project with specified permissions.
Remove a collaborator from the project.
Change a collaborator's role or permissions within the project.