Skip to content
AI

3forge MCP Plugin for AI Coding Tools

3forge publishes 3forge-mcp, a plugin that gives AI coding assistants the skills and agents to author 3forge applications and drive a live instance. First-class targets are Claude Code, Codex, and GitHub Copilot; generated mirrors exist for Gemini and Cursor.

It connects to the MCP server and fetches all 3forge knowledge from the running instance at runtime, so nothing is hard-coded or goes stale.

This is the client-side plugin, not the server

The MCP server is the endpoint inside your 3forge Enterprise deployment. The 3forge-mcp plugin is what you install into your coding tool to connect to that endpoint with a ready-made set of skills, agents, and commands.

Prerequisites

  • A reachable MCP server, a running 3forge Web with the MCP server loaded. By default the REST surface rides the Web component's ports (ami.rest.uses.web.port=web), so the endpoint is https://<host>:<https.port>/3forge_rest/mcp, which is 33333 on a default install. Serving REST from its own plain-HTTP port instead is optional, and covered under MCP server.
  • A supported tool: Claude Code, Codex, or GitHub Copilot (first-class), or Gemini / Cursor (generated mirrors).
  • A git client that can reach GitHub: the plugin installs from the public 3f-git/3forge-mcp marketplace repository.

Install

claude plugin marketplace add 3f-git/3forge-mcp
claude plugin install 3forge-mcp@3forge-mcp-marketplace

Update later with claude plugin marketplace update / claude plugin update; manage with /plugin. Start a new session after installing so the skills, agents, commands, and MCP tools are discovered.

codex plugin marketplace add 3f-git/3forge-mcp --ref main
codex plugin add 3forge-mcp@3forge-mcp-codex
copilot plugin marketplace add 3f-git/3forge-mcp
copilot plugin install 3forge-mcp@3forge-mcp-copilot

Runtime Connection

All 3 first-class tools bundle the 3forge-runtime MCP connection and connect automatically on install, at the endpoint given under Prerequisites.

In Claude Code, target another host by setting AMI_MCP_URL before launching:

export AMI_MCP_URL=https://<host>:<https.port>/3forge_rest/mcp

Over HTTPS the client has to trust the server certificate, which on a fresh install is self-signed. See transport security.

Codex and Copilot do not expand that variable in plugin-provided URLs; to point them at another host, override the 3forge-runtime server in that tool's own MCP configuration.

What You Get

  • Skills, agents, and commands. Over two dozen authoring/runtime skills; 10 agents (for example 3forge-runtime to drive the instance, plus 3forge-sql-builder, 3forge-layout-architect, 3forge-reviewer, 3forge-config-writer); and 6 Claude Code commands (3forge-init, runtime, 3forge-plan, 3forge-query, 3forge-review, 3forge-debug).
  • Namespaced tools. Global tools are prefixed ami_, aidoc_, log_; component tools (center_, web_, relay_) take a componentId first argument. List valid ids with ami_showComponents().
  • A safe-change workflow. The plugin enforces doc → verify → apply: read the relevant docs, run a validation tool if one exists, then apply. Panels and layouts created in a session stay transient until explicitly committed.