Appsai Inc MCP MCP Server

Official MCP server for AppsAI - connect Claude Code to your AppsAI projects

Local serverstdioPython

What is the Appsai Inc MCP MCP server?

Official MCP server for AppsAI - connect Claude Code to your AppsAI projects. Exposed over MCP by the appsai inc mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Build and deploy full-stack apps with AI. This MCP server connects Claude Code, Cursor, Windsurf, and other AI tools to your AppsAI projects.

Its toolset

Everything the assistant can do here goes through one of these:

  • Category — Tools
  • Project — 5
  • Canvas — 25
  • Backend — 18
  • System — 11
  • MongoDB — 18
  • Agents — 9
  • Billing — 15
  • Marketplace — 12
  • Seller — 5
  • Domain — 7
  • Team — 7

Configuration

You will need 2 environment variables: APPSAI_API_KEY, BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 18+ - AppsAI account with credits - API key from Settings > Billing

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @appsai/mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Appsai Inc MCP's toolset — Category, Project, Canvas and 11 more — is a fair guide to whether it matches your workflow. It is maintained by appsai-inc; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Appsai Inc MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Appsai Inc MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the appsai inc mcp mcp server does with a few real requests.

Available tools

ToolWhat it does
CategoryTools
Project5
Canvas25
Backend18
System11
MongoDB18
Agents9
Billing15
Marketplace12
Seller5
Domain7
Team7
Transfer6
Settings4

How to install the Appsai Inc MCP MCP server

{
  "mcpServers": {
    "appsai-inc": {
      "command": "npx",
      "args": ["-y", "@appsai/mcp-server"],
      "env": {
        "APPSAI_API_KEY": "your-value",
        "BASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18+ - AppsAI account with credits - API key from Settings > Billing
VariableDescriptionRequired
APPSAI_API_KEYCredential the server authenticates with.Yes
BASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Appsai Inc MCP to Category.
  • Use Appsai Inc MCP to Project.
  • Use Appsai Inc MCP to Canvas.

Frequently asked questions

It connects Appsai Inc MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Category, Project, Canvas, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Appsai Inc MCP directly.