mcp-archiet 0.1.1

Model Context Protocol server for Archiet — invoke archiet.com codegen from Claude Desktop, Cursor, and Continue.dev.

mcp-archiet

Model Context Protocol server for Archiet. Invoke Archiet's PRD-to-production-ready-app codegen pipeline from any MCP-compatible AI assistant: Claude Desktop, Cursor, Continue.dev, or any other host that speaks MCP.

Archiet turns a Product Requirements Document into a downloadable, zero-touch production-ready application ZIP — across 9 stacks (flask-nextjs, fastapi, django-nextjs, nestjs-nextjs, laravel-nextjs, go-chi, java-spring-boot, rails-nextjs, dotnet-nextjs). This server exposes that pipeline as two MCP tools your AI assistant can call directly.

Install

pip install mcp-archiet

Configure your MCP host

Claude Desktop

Add the server to claude_desktop_config.json (macOS path: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows path: %APPDATA%\Claude\claude_desktop_config.json):

{
  "mcpServers": {
    "archiet": {
      "command": "mcp-archiet",
      "env": {
        "ARCHIET_API_KEY": "ak_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. The archiet server should appear in the MCP indicator.

Cursor / Continue.dev / other MCP hosts

Any MCP host that supports stdio-transport servers can invoke mcp-archiet. Point your host at the mcp-archiet console script and set ARCHIET_API_KEY in the spawning shell's environment.

Get an API key

1. Sign in to archiet.com
2. Visit Settings → API Keys (https://archiet.com/settings/api-keys)
3. Click Create key, give it a name, and copy the ak_... value — it is shown only once
4. Paste it into the ARCHIET_API_KEY environment variable in your MCP host config

API keys require a Professional plan or higher (developer-API access tier).

Tools exposed

archiet.scaffold(prd_text, stack="flask-nextjs")

Submit a PRD to Archiet's codegen pipeline. Returns a download URL for the generated ZIP plus the cert tier outcome.

Arguments:

• prd_text (string, required) — the PRD describing what to build. 200+ characters recommended.
• stack (string, default "flask-nextjs") — one of: flask-nextjs, fastapi, django-nextjs, nestjs-nextjs, laravel-nextjs, go-chi, java-spring-boot, rails-nextjs, dotnet-nextjs.

Returns:

{
  "download_url": "https://archiet.com/api/codegen/jobs/<job-id>/download",
  "cert_tier": "certified",
  "boot_verified": true,
  "quality_score": 92,
  "job_id": "82f74176-5ba5-4620-94fb-b9389f4c695f"
}

archiet.preview_capabilities(prd_text)

Extract the capabilities Archiet would generate for a PRD without running the full codegen pipeline. Useful for previewing scope before spending compute on a real scaffold.

Arguments:

• prd_text (string, required) — the PRD to analyse.

Returns:

{
  "capabilities": [
    {"name": "user_auth", "confidence": 0.98, "description": "Email + password auth with JWT cookies"},
    {"name": "stripe_billing", "confidence": 0.91, "description": "Subscription billing with Stripe Checkout"},
    {"name": "rbac", "confidence": 0.74, "description": "Role-based access control across workspaces"}
  ]
}

Example usage

In Claude Desktop, ask:

Use archiet to scaffold a B2B SaaS for project management. The product is a Kanban-style task board with team workspaces, comment threads on cards, file attachments, and integrations to Slack and GitHub. Use the flask-nextjs stack.

Claude will invoke archiet.scaffold with that PRD and return a download URL you can grab.

For preview-only:

Use archiet to preview what capabilities you'd build for a customer-success dashboard with NPS surveys, churn prediction, and Mixpanel events.

Claude will invoke archiet.preview_capabilities and show the inferred capability list before you commit to a full scaffold.

Environment variables

Variable	Default	Purpose
ARCHIET_API_KEY	(required)	Bearer API key, get one at https://archiet.com/settings/api-keys
ARCHIET_API_BASE_URL	https://archiet.com	Override for self-hosted or staging archiet.com deployments
ARCHIET_API_TIMEOUT_SECONDS	600	HTTP timeout per request (codegen jobs can take several minutes)

Where this fits

This MCP server is a transport layer only — it makes no LLM calls of its own. Every tool wraps a public archiet.com HTTP endpoint authenticated by your workspace API key. The actual codegen work happens on archiet.com servers; this client just shuttles requests and responses across the MCP boundary so any MCP-compatible AI assistant can drive Archiet without a custom integration.

If you want to invoke Archiet from a non-MCP script, use the HTTP API directly — see https://archiet.com/api/v1/schema for the OpenAPI spec.

Links

• Archiet: archiet.com
• API docs: archiet.com/docs
• Source / issues: github.com/aniekanasuquookono-web/archiet
• MCP protocol: modelcontextprotocol.io

License

Apache-2.0. See LICENSE.