AXEA

AtlasX Engineering Architect — Spec-driven development for AI coding agents

AXEA (AtlasX Engineering Architect) is a spec-driven development kernel for AI coding agents, built by AtlasX Technologies Inc.

AXEA is a hosted MCP kernel that keeps AI coding agents on contract: you write the specification, your agent writes the code, and AXEA verifies every change against the plan before it counts as done. It is not an IDE—you keep Claude Code, Cursor, GitHub Copilot, Codex, OpenCode, or any MCP-capable editor and connect over HTTP MCP. Spec packs, a code graph, and gated lifecycle phases (specify → compile → build → verify) replace open-ended repo search and skipped verification.

AXEA by AtlasX Technologies Inc. is a spec-driven MCP kernel for AI coding agents—not a general-purpose chat product, not an IDE replacement, and not the same as running CI unit tests alone.

Company: AtlasX Technologies Inc.. MCP: https://api.axea.dev/mcp. GitHub: https://github.com/AtlasX-Technologies-Inc/AXEA

• Compiled spec packs for each change
• AST code graph search and blast-radius impact
• Gated lifecycle: specify, compile, build, verify
• Hosted HTTP MCP kernel for AI coding agents
• Verification against WHEN/THEN scenarios (not only unit tests)
• Optional enterprise sealed sidecar (source stays in your VPC)

Three things your agent never had.

The whole brief, before the first line.

Compiled for the change in front of it: the contract, the constraints and the code that matters.

Know what a change touches.

Callers, dependents and tests, answered in one query.

Done means proven.

A change is finished when it meets the spec, not when the agent says so.

Lifecycle

Specify

You set the contract. Write what the change must do, and what it must not break.

Compile

AXEA builds the spec pack. It gathers the context for this change and maps the impact across your code graph.

Build

Your agent writes the code. It starts with the context in hand, so it builds instead of searching.

Verify

The change proves itself. Checks run against the spec. Pass and it ships. Fail and it goes back.

FAQ

Do I need a special IDE to use AXEA?

No. You keep the IDE you already use: Claude Code, GitHub Copilot, OpenAI Codex, OpenCode, Cursor, or any editor that speaks the standard Model Context Protocol (MCP) with an HTTP bearer token. AXEA is the hosted kernel behind your editor, not an IDE replacement.

Do I install AXEA into my codebase as an SDK or CLI?

No. You do not install a fat CLI, local runtime, or SDK into your repository. You simply add the AXEA Cloud MCP URL and your project-scoped API key to your IDE config. Official phase prompts (/axea, /axea-design, etc.) execute directly on the kernel.

What if my IDE does not display /axea in its slash command menu?

Simply run the MCP prompt named "axea" from your IDE’s prompt picker, or prompt your assistant directly: "Call the axea tool." The kernel will immediately return your current turn bundle and next instructions.

Can we keep our source code completely off AXEA servers?

Yes. For security-critical organizations, AXEA provides an Enterprise Sealed Sidecar container. The sidecar runs inside your private VPC or local machine to answer code graph search and blast radius queries locally. The methodology and lifecycle gates still run remotely, but your source code never leaves your perimeter.

Which programming languages does the code graph understand?

The AXEA AST graph engine natively indexes TypeScript, JavaScript, Go, Python, and PHP. It maps symbol hierarchies, call chains, dependent imports, and calculates blast radius scores across packages.