ARCHLEXOSS

Built for LLMs and MCP

Cloud diagrams.
Built for agents.

Ask Claude, Cursor or Codex to map AWS, Cloudflare, GCP and Kubernetes. Get checked source, a rendered diagram and a link to keep editing in the playground.

Connect free MCP Open playground

Free to use. No API keys or account required.

Try this prompt with your agent

Diagram Cloudflare Workers proxying requests to AWS Lambda and publishing to GCP Pub/Sub, with both paths connected to a Kubernetes workload. Validate it and give me a playground link.

Cloudflare, Inc. and contributors; CC BY 4.0; https://creativecommons.org/licenses/by/4.0/; source: https://github.com/cloudflare/cloudflare-docs/blob/48f601bf4293fa9032505f858656d0db5b559131/src/icons/workers.svg; changes: sanitized SVG, white backing added, monochrome ink recolored to #f6821f; original glyph geometry retained. No Cloudflare endorsement. CLUSTER production NAMESPACE orders
Cloudflare, Inc. and contributors; CC BY 4.0; https://creativecommons.org/licenses/by/4.0/; source: https://github.com/cloudflare/cloudflare-docs/blob/48f601bf4293fa9032505f858656d0db5b559131/src/icons/workers.svg; changes: sanitized SVG, white backing added, monochrome ink recolored to #f6821f; original glyph geometry retained. No Cloudflare endorsement. CLUSTER production NAMESPACE orders
Cloudflare, Inc. and contributors; CC BY 4.0; https://creativecommons.org/licenses/by/4.0/; source: https://github.com/cloudflare/cloudflare-docs/blob/48f601bf4293fa9032505f858656d0db5b559131/src/icons/workers.svg; changes: sanitized SVG, white backing added, monochrome ink recolored to #f6821f; original glyph geometry retained. No Cloudflare endorsement. CLUSTER production NAMESPACE orders
Cloudflare, Inc. and contributors; CC BY 4.0; https://creativecommons.org/licenses/by/4.0/; source: https://github.com/cloudflare/cloudflare-docs/blob/48f601bf4293fa9032505f858656d0db5b559131/src/icons/workers.svg; changes: sanitized SVG, white backing added, monochrome ink recolored to #f6821f; original glyph geometry retained. No Cloudflare endorsement. CLUSTER production NAMESPACE orders
Cloudflare + AWS + GCP + Kubernetes. One checked source.Edit this architecture

  1. Ask your LLM.

    Describe your system. The agent skill supplies the language, provider rules and examples.

  2. Let MCP do the checking.

    Cloud catalogs, validation and rendering, with tools, prompts and documentation ready for your agent.

  3. Make it yours.

    Open the same source in the playground. Inspect, edit and export your architecture.

Made for your agent.
Ready for you.

Connect the free MCP server or install the skill. Let your LLM draw, then inspect and refine the same source in the playground.

Connect your agent to the whole picture.

Give your agent cloud catalogs, semantic validation, diagram rendering and editable playground links. Works with any MCP-compatible client.

Client setup instructions
Streamable HTTP
https://mcp.archlex.dev/mcp

Free to use. No API keys or account required.

Agent setup
Read the prompt

Set up the ArchLex MCP server in the MCP-capable client or coding-agent environment I am currently using (Claude Code, Cursor, Codex, VS Code/Copilot, or another compatible client). Use the remote Streamable HTTP endpoint https://mcp.archlex.dev/mcp and name the server archlex. It is free to use and requires no API key, account, or authentication headers. If this environment does not support MCP, explain that and suggest a compatible client. Otherwise, detect this client's supported setup method and configuration scope. Add or update only the ArchLex entry; preserve all other MCP servers and settings. If you cannot access the configuration, give me the exact client-specific steps instead of claiming it is configured. Connect to the server and verify that render_diagram, validate_diagram, get_cloud_catalog, and generate_playground_url are available. If a client restart or permission approval is needed, explain what I need to do and verify again afterward. Once connected, render a small example using render_diagram, show the result if supported, and provide the returned editable playground link. Report any setup or connection errors accurately.

An LLM workflow, with a human workspace. Explore the playground

Your agent writes it.
ArchLex checks it.

Resources have an identity. Connections have rules. Give your agent a language that understands both.

Try this AWS example: change a supported connection, inspect the real provider warning, then correct it.

Explore the agent workflow
orders.archlex✓ Checks passed
AWS / Serverless API3 resources · 2 connections
Inspect
SourcePlain text. Real relationships.
provider aws
direction LR
api: api-gateway["API Gateway"]
worker: lambda["Order handler"]
data: dynamodb["Orders"]
api -[invokes]-> worker
worker -[writes]-> data
A function writes to a database.

Lambda → DynamoDB is a supported “writes” relationship.

Checked against AWS diagram rulesEdit in playground

Every connection
has a meaning.

A line is easy to draw. ArchLex checks what it connects, where resources belong, and what the relationship says.

Resources with an identity

Lambda is a function. DynamoDB is a database. Provider catalogs give each node more than a label.

Relationships with rules

“Invokes” and “writes” mean different things. Supported endpoints are checked against provider declarations.

Boundaries that belong

Accounts, regions, VPCs, subnets and namespaces describe structure. ArchLex checks supported placement rules.

orders.archlexOne relationship changed
 api: api-gateway
 worker: lambda
 data: dynamodb
 
 api -[invokes]-> worker
− worker -[invokes]-> data
+ worker -[writes]-> data
A supported connection. A readable change.

Small changes.
Clear reviews.

Your diagram lives in plain text. Review the relationship that changed, keep the source in Git, and render it as SVG.

Make your first change

The clouds you work in.

Provider-aware resources and official icons.
Mix providers in one diagram when your architecture does.

A few useful answers.

What does ArchLex actually validate?

Declared diagram rules: known resources, supported scopes and typed relationship endpoints. It checks your architecture description against provider catalogs. It does not inspect a deployed system or certify its security or availability.

Can I use it with my coding agent?

Yes. ArchLex is built for LLM workflows: connect the free hosted MCP server or install the agent skill. Claude Code, Cursor, Codex and other compatible clients can look up resources, validate source, render diagrams and return an editable playground link.

Is the MCP server free?

The hosted MCP server is free to use, with no API keys or account required. The playground is free too. ArchLex is open source under the MIT license, and you can also run the CLI or packages locally.

Can I use it without an AI agent?

Yes. Write a diagram in the playground, render it with the CLI, or embed @archlex/core in a browser or Node.js application. The source is plain text and the output is SVG.

Your next diagram
starts with a prompt.

Bring your agent. The MCP server and playground are ready.

Connect your agent for free