MCP-native

Every API you build is auto MCP-enabled.

NoStackAI runs a real MCP (Model Context Protocol) server - nothing to expose manually, no integration to write. Mint an API key, point Claude Code, Claude Desktop, or Cursor at it, and the AI can read your platform's capabilities and build entities, logic blocks, events, and connectors directly - no more copy-pasting a spec back and forth.

Create an entity and its CRUD endpoints are instantly callable by the same AI - the live API reference and your current entity list are both served over the same MCP connection
One MCP server covers every API category: entities, logic blocks, events, connectors, AI providers, roles
Works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client
Scoped API keys are dev-only by default - a connected AI can never touch production
No custom MCP server to write or host - it's already running for every org

Generate your key See setup instructions

Tools

28 tools, grouped by what they act on.

Every tool below is live on the server today - not a roadmap. Read tools (list_*/describe_*) need no destructive confirmation; write tools (create_*/update_*/delete_*) act on your org the moment the AI calls them.

Platform capabilities

get_platform_capabilities Returns nostackai's full capability spec - column/index types, event types, formula syntax, logicblock step types, connector shapes, ai_call intents. Call this first to ground everything else.

Entities

`list_entities`	Lists the org's existing entities (name + api definition summary).
`describe_entity`	Returns one entity's full api definition (fields, keys, views) by name.
`create_entity`	Creates a new entity - fields, key template, indexes, views, and public-access rules.

Events (automations)

`list_events`	Lists an entity's active events - notifications, webhook calls, entity writes triggered on create/update.
`describe_event`	Returns one event definition by id.
`create_event`	Creates a new event on an entity (trigger stage, conditions, destination config).
`update_event`	Updates an existing event definition. Only fields provided are changed.
`delete_event`	Deletes an event definition by id.

Logic blocks

`list_logicblocks`	Lists the org's logic blocks (custom serverless API endpoints built from typed steps).
`describe_logicblock`	Returns one logic block by apiname, including its full step/formula/variable definition.
`create_logicblock`	Creates a new logic block from a steps/variables/formulas definition.
`update_logicblock`	Merges the given fields into an existing logic block's definition.
`toggle_logicblock`	Enables or disables a logic block without touching its definition.
`delete_logicblock`	Deletes a logic block by apiname.

Agents (crews)

`list_crews`	Lists the org's agent crews (multi-agent automations).
`describe_crew`	Returns one agent crew by id, including its graph/guardrails/memory config.
`create_crew`	Creates a new agent crew from a node/edge graph.
`update_crew`	Updates an existing crew's graph, memory, or status.

Roles & ACL

`get_role_acl`	Returns the org's role catalog - each role's name, title, active state, and ACL (allowed route patterns).
`update_role_acl`	Replaces the full role list (must include org_admin and developer).

Connectors

`list_connectors`	Lists the org's enabled connectors (Slack, email, SMS, webhooks, etc.).
`describe_connector`	Returns one connector's credential schema and action input schemas.
`setup_connector`	Enables and configures a connector for the org.
`disable_connector`	Disables a connector for the org and removes its definition.

AI providers

`list_ai_providers`	Lists the org's AI provider catalog (seeded + custom) used by logic blocks/agents.
`set_ai_provider`	Adds or updates an AI provider (Anthropic, OpenAI, Gemini, or a custom OpenAI-compatible endpoint).
`remove_ai_provider`	Removes a provider from the org's AI catalog.

Plus one MCP resource, nostackai://api-reference: the full REST API reference (CRUD shapes, filter/pagination syntax, auth, multi-tenancy, event types) for every entity/logic block/event the tools above create.

MCP server URL

One URL, every client.

The server URL below is the same for every org - only the bearer key differs. Generate a key to fill it in.

https://dev-cp.nostackai.com/apistudio/mcp

◊

Setup

Connect your AI client.

Never used one of these before? Full setup, step by step. Replace <YOUR_MCP_API_KEY> with the key you generate.

Claude Code (terminal CLI)

Install Node.js 18+ if you don't have it (nodejs.org), then install Claude Code:
```
npm install -g @anthropic-ai/claude-code
```
Open a terminal in any project folder and run claude. The first time, it opens your browser to sign in (or asks for an API key) - follow the prompts.
Generate a key above, then run this once to connect nostackai (paste it into the same terminal, outside the claude session - or inside it, prefixed with !):
```
claude mcp add --transport http nostackai https://dev-cp.nostackai.com/apistudio/mcp --header "Authorization: Bearer <YOUR_MCP_API_KEY>"
```
Verify it worked: start (or restart) claude in that folder, type /mcp, and confirm nostackai is listed. Or just ask it: "what nostackai tools do you have?"

Claude Desktop (Mac/Windows app)

Install the app from claude.ai/download if you haven't. You'll also need Node.js installed locally - Desktop uses it to bridge to nostackai's remote server.
Open Claude Desktop → Settings (gear icon, or the Claude menu on Mac) → Developer tab → Edit Config. This opens (or creates) a file called claude_desktop_config.json in your file editor.

Paste this in. If the file already has an mcpServers section with other servers in it, add just the "nostackai": {...} part into that existing object instead of replacing the whole file:

{
  "mcpServers": {
    "nostackai": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://dev-cp.nostackai.com/apistudio/mcp",
        "--header",
        "Authorization: Bearer <YOUR_MCP_API_KEY>"
      ]
    }
  }
}

Save the file, then fully quit Claude Desktop and reopen it - closing the window isn't enough, quit it from the menu or system tray.
Verify it worked: start a new chat and look for a tools icon near the message box - nostackai should be listed there with its tools available to toggle on.

Cursor

Install Cursor from cursor.com if you haven't, and sign in.
Open Cursor Settings (gear icon, or Cmd/Ctrl+Shift+J) → search for MCP → Add new MCP server. Or, if you'd rather edit the file directly, create .cursor/mcp.json in your project folder (or ~/.cursor/mcp.json to make it available in every project).

Paste this in (merge into an existing mcpServers object if you already have other servers configured):

{
  "mcpServers": {
    "nostackai": {
      "url": "https://dev-cp.nostackai.com/apistudio/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_API_KEY>"
      }
    }
  }
}

Cursor usually picks it up automatically. If it doesn't show up, reload the window: Cmd/Ctrl+Shift+P → "Reload Window".
Verify it worked: back in Cursor Settings → MCP, nostackai should show a green/active status with its tool count. You can also ask Cursor's chat to list its available MCP tools.

Once connected, ask the AI to call get_platform_capabilities first - it grounds every column type, event type, and step type it uses in what nostackai actually supports.

Ready to connect an AI client?

Generate your key