Skip to content

MCP is a way into the gate.

If your coding agent, editor, or internal tool already uses MCP, Novyx can expose governed action workflows there.

Do not adopt Novyx because it has a long memory-tool menu. Adopt it because MCP lets your agent request production-changing actions through a control plane.

Protect an actionLearn Control

MCP config

Governed agent access

json
{
  "mcpServers": {
    "novyx-control": {
      "command": "uvx",
      "args": ["novyx-mcp"],
      "env": {
        "NOVYX_MODE": "control"
      }
    }
  }
}

Configure MCP where your agent runs, then route production effects through Novyx actions.

What MCP should expose

A small action surface beats a giant memory menu.

The useful MCP workflow is compact: request a protected action, attach blast-radius evidence, check the decision, and inspect the audit trail.

request_action

Submit an intended production effect for review.

get_decision

Read allow, deny, approval, or multi-approval status.

attach_blast_radius

Send affected systems, records, jobs, customers, and rollback notes.

read_audit_trail

Inspect evidence for a request, approval, execution, or recovery event.

Keep MCP in the docs lane.

MCP is important for developer adoption, but the public front door should be action governance. This page stays available for technical buyers without making the old memory category the homepage story.

Good: Claude Code requests a migration through Novyx
Good: Cursor attaches file diff and affected services
Good: Internal agent reads approval status before execution
Old story: a large memory-tool count as the main value prop