AICre8 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AICRE8_API_KEY | Yes | Your API key (starts with ak_live_) | |
| AICRE8_API_URL | No | API base URL | https://aicre8.dev/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all your AICre8 projects with their IDs, names, and preview URLs |
| create_projectA | Create a new AICre8 project. Returns the project ID and URL ID. |
| 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. |
| read_fileA | Read a file from the project sandbox. Requires an active sandbox (run generate_code first to boot it). |
| write_fileA | Write or update a file in the project sandbox. Creates parent directories automatically. |
| run_commandA | Execute a shell command in the project sandbox (e.g. npm install, npm run build). Max timeout 5 minutes. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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).
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.
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.
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.