Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mage.ai/llms.txt

Use this file to discover all available pages before exploring further.

Mage Agent connects your local development environment to your Mage Pro cluster through the Model Context Protocol (MCP). Your AI assistant can inspect, create, modify, and run Mage pipelines using natural language — and a built-in sync engine keeps local files in step with the cluster.

Quickstart

Get connected in under five minutes.

IDE Integration

Connect Cursor, Claude Code, or Codex CLI.

Sync

Mirror your Mage project to local files.

MCP Tools

Full reference for every tool your AI can call.

​
How it works

Your AI assistant  ──MCP──►  mage-agent  ──REST──►  Mage Pro cluster
      │                           │
      │                     sync engine
      └── local files ◄──────────┘
  1. MCP server — mage-agent runs as a background stdio process. Your IDE or AI agent sends tool calls over JSON-RPC; mage-agent translates them into Mage Pro REST API requests.
  2. Skill resources — the server exposes Markdown guidance files that give your AI assistant context on how to interact with pipelines, blocks, runs, and sync operations.
  3. Sync engine — a separate CLI layer lets you pull the full remote project tree to a local directory, push local edits back, and resolve conflicts file by file.

​
Supported clients

Cursor

Claude Code

OpenAI Codex CLI

Any MCP-compatible client that can launch a subprocess will work with the same configuration.