Name: AppsAI
Author: appsai-inc

LABSCO SUMMARY

The whole platform, including the parts you normally leave the editor for.

Most build-and-deploy servers stop at the deploy; this one keeps going into custom domains, collaborator permissions, marketplace publishing and the credit balance, which means an agent can carry a project from first component to live URL without handing back. Worth knowing before you start: the same key that edits code also spends money and changes team access.

What it is

The control surface for AppsAI projects, reachable from Claude Code, Cursor, Windsurf and other clients. It spans the whole lifecycle: editing React components, writing backend code, provisioning AWS, deploying, attaching a domain, inviting collaborators, and paying for it.

What you get

Canvas — React components, styles and assets; Backend — backend code, S3 and CloudFormation
MongoDB — database and collection management; Agents — prompt management and versioning
system_DEPLOY_FRONTEND, system_DEPLOY_BACKEND and system_DEPLOY_ALL, with system_GET_ENVIRONMENT_STATUS for URLs
system_ADD_MCP_SERVER and system_LIST_MCP_SERVERS — your project can itself connect to other MCP servers
Domains: domain_CHECK_AVAILABILITY, domain_ADD_CUSTOM_DOMAIN, domain_VERIFY_CUSTOM_DOMAIN
Team and marketplace: team_INVITE_COLLABORATOR, marketplace_PUBLISH_TEMPLATE, marketplace_FORK_TEMPLATE
Billing in-band: billing_GET_AVAILABLE_CREDITS, billing_GET_CURRENT_PLAN, billing_ADD_FUNDS
Resources appsai://projects and appsai://project/{id} carry project context and file structure
Starter prompts including build-youtube, build-slack and build-twitter

Requirements

An AppsAI account and an API key from Settings → Billing → API Keys, shown once, set as APPSAI_API_KEY. Your client runs npx -y @appsai/mcp-server — Claude Code adds it in one command. Stacks covered are Next.js with Tailwind and shadcn/ui on the front, several backend choices, MongoDB Atlas and AWS behind. Agents can also register themselves with a wallet signature and top up credits with USDC on Ethereum, Base, Arbitrum or Polygon. Version 1.0.13.

Setup effort

One command plus a key — npx -y @appsai/mcp-server, then supply credentials

See installation options

USE CASES

01

Getting a new app live

Create the project, edit the components, deploy both halves, then read back the environment URLs.

system_DEPLOY_ALLsystem_GET_ENVIRONMENT_STATUS

02

Putting a real domain in front of it

Check the name, add the custom domain, then verify the DNS from the same conversation.

domain_CHECK_AVAILABILITYdomain_ADD_CUSTOM_DOMAINdomain_VERIFY_CUSTOM_DOMAIN

03

Giving your project access to another service

Attach an external MCP server to the project so the agents inside it gain those tools.

system_ADD_MCP_SERVERsystem_LIST_MCP_SERVERS

37 tools

Listed in project docs. Your client may show a different list.

system_DEPLOY_BACKEND

system_DEPLOY_FRONTEND

system_DEPLOY_ALL

system_GET_ENVIRONMENT_STATUS

system_GET_DEPLOY_ARTIFACTS

system_CONNECT_APP

system_DISCONNECT_APP

system_ADD_MCP_SERVER

system_LIST_MCP_SERVERS

system_UPDATE_MCP_SERVER

system_REMOVE_MCP_SERVER

billing_GET_CURRENT_PLAN

billing_CREATE_CHECKOUT

billing_GET_PORTAL_SESSION

billing_ADD_FUNDS

BEFORE YOU INSTALL

What to know first

Tools you get

37 tools named in the project's documentation.

Requires

npx on PATH
Node.js 18+
APPSAI_API_KEY in your environment

Where it runs

All 4 documented clients run the server on your machine.

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y @appsai/mcp-server

MCP Clients

Claude Code

CLAUDE CODE · TERMINAL

claude mcp add appsai -e APPSAI_API_KEY=<YOUR_APPSAI_API_KEY> -- npx -y @appsai/mcp-server

Claude Desktop, Cursor, Windsurf

JSON

{
  "mcpServers": {
    "appsai": {
      "command": "npx",
      "args": [
        "-y",
        "@appsai/mcp-server"
      ],
      "env": {
        "APPSAI_API_KEY": "<YOUR_APPSAI_API_KEY>"
      }
    }
  }
}

AppsAI