# archstone

Compiler that turns declarative YAML specs and OpenAPI schemas into ready-to-use MCP tools without handwritten integration glue code.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 6
- Author: NousVigil
- License: Apache-2.0 · policy=link-only · description only; the file stays with the author
- Source: https://github.com/NousVigil/archstone
- Updated: 2026-10-22
- HTML: https://affpapa.org/en/nevibecode/mcp/archstone

## What it does

Archstone takes business capability declarations written in CDL (Capability Definition Language) and lowers them to an intermediate representation. Bindings map these definitions directly to REST endpoints or PostgreSQL databases, which `archstone serve` then exposes over stdio or HTTP as agent tools. The `archstone init` command can also scaffold a manifest directly from an OpenAPI file or a Postgres schema.

The compiler filters data flow in both directions. Backend attributes omitted from the manifest never reach the prompt context. Invented fields produced by an LLM get rejected before reaching production endpoints. For continuous integration, `archstone verify` replays recorded fixtures against target backends to spot API drift.

Running the CLI requires Node 22+. Both `archstone build` and `archstone serve` operate entirely offline without network pings or API tokens.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add archstone -- npx -y @archstone/cli
```

### Codex

**Platform CLI**
```bash
codex mcp add archstone -- npx -y @archstone/cli
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "archstone": {
            "command": "npx",
            "args": [
                "-y",
                "@archstone/cli"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "archstone": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@archstone/cli"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add archstone npx -y @archstone/cli
```

## When to use it
- turn an OpenAPI document into MCP tools without handwritten glue
- prevent undeclared backend database columns from leaking into agent prompts
- block hallucinated model arguments before reaching internal APIs
- catch backend contract drift with automated fixture replays

## Example prompts
- Draft an Archstone capability manifest from `openapi.yaml` for the catalog domain
- Validate and compile manifests inside `manifest` using `archstone apply`
- Serve MCP tools via stdio from directory `manifest` using `archstone serve`

## Similar
- [MCP Toolbox for Databases](https://affpapa.org/en/nevibecode/mcp/googleapis-mcp-toolbox-for-databases.md) — MCP server · ★ 16730
- [PostHog MCP Server](https://affpapa.org/en/nevibecode/mcp/posthog-mcp-server.md) — MCP server · ★ 40459
- [OpenWork MCP Gateway](https://affpapa.org/en/nevibecode/mcp/openwork-mcp-gateway.md) — MCP server · ★ 24271
- [Keploy](https://affpapa.org/en/nevibecode/mcp/keploy.md) — MCP server · ★ 18779
- [Nhost](https://affpapa.org/en/nevibecode/mcp/nhost.md) — MCP server · ★ 9369
- [basebalance.cloud — x402 RPC & MCP gateway](https://affpapa.org/en/nevibecode/mcp/basebalancecloud-x402-rpc-mcp-gateway.md) — MCP server · ★ 7548

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md