Skip to main content
Glama

@aicre8/mcp-server

MCP server for AICre8 — connect AI agents to create, edit, and deploy web projects.

Works with Claude Desktop, Cursor, Claude Code, and any MCP-compatible client.

Setup

1. Get an API Key

Go to aicre8.dev/settings and create an API key in the API Keys section.

2. Configure Your Client

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "aicre8": {
      "command": "npx",
      "args": ["@aicre8/mcp-server"],
      "env": {
        "AICRE8_API_KEY": "ak_live_your_key_here"
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project or global config:

{
  "mcpServers": {
    "aicre8": {
      "command": "npx",
      "args": ["@aicre8/mcp-server"],
      "env": {
        "AICRE8_API_KEY": "ak_live_your_key_here"
      }
    }
  }
}

Claude Code

claude mcp add aicre8 -- npx @aicre8/mcp-server

Set AICRE8_API_KEY in your environment.

3. Start Using

Once configured, ask your AI agent things like:

  • "List my AICre8 projects"

  • "Create a new project called Coffee Shop"

  • "Build a landing page with a dark theme and hero section"

  • "Deploy the project"

Related MCP server: Prowpt MCP Server

Available Tools

Tool

Description

list_projects

List all your projects

create_project

Create a new project

generate_code

Generate or modify code with AI

read_file

Read a file from the project sandbox

write_file

Write a file to the project sandbox

run_command

Run a shell command in the sandbox

deploy_project

Deploy to a live branded URL

Environment Variables

Variable

Required

Default

Description

AICRE8_API_KEY

Yes

—

Your API key (starts with ak_live_)

AICRE8_API_URL

No

https://aicre8.dev/api/v1

API base URL

API Documentation

Full REST API docs: aicre8.dev/developers

License

MIT

Available Tools

7 tools
create_projectA

Create a new AICre8 project. Returns the project ID and URL ID.

Inputs: name, access_type.

deploy_projectC

Deploy the project to a live branded URL (e.g. my-project.aicre8.app). Pass a map of file paths to contents. Use b64 prefix for binary file content.

Inputs: project_id (required), files (required).

generate_codeA

Send a prompt to generate or modify code in an AICre8 project using AI. The AI will write files, install packages, and update the project. Costs 1 credit per call.

Inputs: project_id (required), prompt (required), chat_mode.

list_projectsA

List all your AICre8 projects with their IDs, names, and preview URLs

Inputs: no named parameters.

read_fileA

Read a file from the project sandbox. Requires an active sandbox (run generate_code first to boot it).

Inputs: project_id (required), file_path (required), encoding.

run_commandA

Execute a shell command in the project sandbox (e.g. npm install, npm run build). Max timeout 5 minutes.

Inputs: project_id (required), command (required), cwd, timeout_ms.

write_fileA

Write or update a file in the project sandbox. Creates parent directories automatically.

Inputs: project_id (required), file_path (required), content (required), encoding.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_project, deploy_project, generate_code, list_projects, read_file, run_command, and write_file all target specific actions in the AICre8 project lifecycle. An agent can easily distinguish between them, such as separating file operations (read_file, write_file) from project management (create_project, list_projects) and execution (run_command, generate_code).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case, such as create_project, deploy_project, generate_code, list_projects, read_file, run_command, and write_file. This uniformity makes the tool set predictable and easy to navigate, with no deviations in style or convention.

    Tool Count5/5

    With 7 tools, the server is well-scoped for managing AICre8 projects, covering creation, deployment, code generation, listing, and file/sandbox operations. Each tool earns its place by addressing a core aspect of the workflow, avoiding bloat while ensuring comprehensive functionality for the domain.

    Completeness4/5

    The tool set provides strong coverage for AICre8 project management, including CRUD-like operations (create, list, deploy) and sandbox interactions (read/write files, run commands, generate code). A minor gap exists in the lack of update or delete operations for projects, but agents can work around this by managing files or regenerating code as needed.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides secure, sandboxed file system access for AI assistants to read, write, and manage project files with controlled command execution capabilities, all confined to a designated workspace directory.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to run shell commands, spawn persistent background tasks, and read/write files inside isolated remote container sandboxes on a VPS. It also provides project workspace listing, task attach/kill controls, and a searchable knowledge graph for memory continuity across sessions.
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to manage and execute development commands within isolated Railway sandboxes, providing a remote shell, file read/write, and sandbox lifecycle management for running tests, builds, and repository operations.
      -