Model Context Protocol

Drive the Workshop from your own coding agent

A standard MCP server that makes Claude Code, Copilot or Codex a DMX expert — reading, writing and validating your specs with a platform-scoped Workshop key. It runs on your Pro plan, on your machine. Tools, not an LLM — and it can never trigger a compile.

Get a Workshop keySee the VS Code extension
How it fits

Your agent, your specs

The MCP sits between the coding agent you already run and your canonical specs — the same ones the Workshop edits.

Your coding agent
Claude Code · Copilot · Codex — your Pro plan, your machine
MCP / HTTPS
DevMatrix MCP
Tools, not an LLM · scoped Workshop key · never compiles
authored
Your specs & wiki
Read, validate, version and ground — same canonical specs as the Workshop
In practice

What your agent can do

Point it at a platform and it authors like a teammate who already knows your codebase — within a key that grants spec and wiki access only.

Draft specs from intent

Describe a feature in plain language — or hand it a ticket — and your agent writes valid DMX, grounded in the platform you already have.

Validate before it ships

Every spec is checked against the live compiler grammar, so a broken spec is caught in your editor instead of halfway through a build.

Refactor across versions, safely

As your agent edits, each change is saved as a new revision — nothing is overwritten, and any earlier version can be restored.

Answer with your platform's truth

Suggestions and edits are grounded in your platform wiki and your real specs — with citations — not generic guesses.

Expert from the first prompt

Built-in language reference, grammar and authoring guidance make any capable agent fluent in DMX immediately — no ramp-up.

Scoped, and it never compiles

A platform-scoped key grants spec and wiki access only. Your agent can read and write — but it can never trigger a compile or touch anything else.

Grounding

What is the platform wiki?

The knowledge that makes your agent's answers yours, not generic.

Every platform gets its own wiki — a private knowledge base built from your own Markdown: architecture decisions, domain glossaries, API contracts, naming conventions, anything your team relies on.

DevMatrix indexes it so the AI — both the Workshop architect and your own coding agent — reads, answers and edits grounded in your documentation, citing the exact page it used instead of guessing. It's how you teach the AI about your platform.

  • Upload Markdown — single files or whole folders, kept versioned.
  • Indexed for retrieval — every answer cites the wiki page it came from.
  • Shared by the Workshop architect and your MCP agent alike.
Connect

Plug it into your agent

First-class setup for Claude Code, and a standard HTTP endpoint for any MCP-capable client.

Claude Code (terminal)

Install the DevMatrix plugin and your key is stored in the OS keychain — no plaintext config.

claude-code
/plugin marketplace add devmatrix-ai/devmatrix-mcp
/plugin install devmatrix@devmatrix

Any MCP client

The MCP is a standard HTTP server — point Copilot agent mode, Codex or any MCP-capable client at it with your Workshop key.

.mcp.json
{
  "mcpServers": {
    "devmatrix": {
      "type": "http",
      "url": "https://mcp.devmatrix.dev/mcp",
      "headers": {
        "Authorization": "Bearer dm_live_your_key_here"
      }
    }
  }
}

Also connects to Claude.ai (web & desktop) as an OAuth custom connector — and any other MCP-capable client.

Make your agent a DMX expert

Grab a scoped Workshop key and connect the coding agent you already run.

Get startedExplore the tooling