Install Forge

Step 1 · Install

Pick your AI coding tool.

Each plugin connects your tool to Forge and keeps every run on its rails. A free account is created when you sign in.

1

Add the ShipToday marketplace and install Forge

Run these two commands inside Claude Code:

/plugin marketplace add ShipToday/forge-plugin-claude-mp
/plugin install forge-shiptoday@shiptoday

2

Sign in

Run /mcp, choose forge, and sign in when prompted. New accounts are free.
3

Run setup

Type forge, help our team get set up and follow along.

Updating later: /plugin marketplace update shiptoday. Source on GitHub.

1
Add the ShipToday marketplace and install Forge
From the Codex CLI:
```
codex plugin marketplace add ShipToday/forge-plugin-codex
```
Then run /plugins, open the shiptoday marketplace, and install Forge.

In the Codex app instead: Plugins → ⋯ → Add marketplace, source ShipToday/forge-plugin-codex, git ref main, then install Forge from the shiptoday marketplace.
2
Turn on plugin hooks
Codex ships with plugin hooks off. Forge's routing and guardrails need them — add this to ~/.codex/config.toml:
```
[features]
plugin_hooks = true
```
3

Sign in

Codex prompts you to sign in to forge the first time it connects. New accounts are free.
4

Run setup

Type forge, help our team get set up and follow along.

Token usage is captured from Codex's own session log on Codex 0.131.0 or newer. Source on GitHub.

1
Add the plugin from its repository link
Open Cursor Settings → Plugins and paste this into Search or Paste Link:
```
https://github.com/ShipToday/forge-plugin-cursor
```
2

Sign in

Open Cursor Settings → Tools & MCP, find forge, and click Sign In. New accounts are free.
3

Trust the hooks

Review and trust Forge's hooks under Cursor Settings → Hooks. They power the workflow guardrails and need Node.js on your PATH.
4

Run setup

Type forge, help our team get set up and follow along.

Marketplace listing coming soon. Cursor doesn't expose per-session token usage to plugins, so Token Intelligence reports Cursor sessions as not measured. Source on GitHub.

1
Add the Forge MCP server
Forge speaks MCP, the open Model Context Protocol, over HTTP. Add it wherever your client configures servers:
```
{
  "mcpServers": {
    "forge": { "url": "https://teams.shiptoday.ai/mcp" }
  }
}
```
2

Sign in

The server uses OAuth — your client prompts you to sign in the first time it connects. New accounts are free.
3

Run setup

Type forge, help our team get set up and follow along.

What you get this way: every Forge workflow, triggered by saying forge, … in your prompt. The Claude Code, Codex, and Cursor plugins add automatic intent routing and step guardrails. Token capture is available in Claude Code and supported Codex versions; Cursor usage is currently unmeasured.

Step 2 · Set up

Choose your first useful workflow.

Setup recommends a starter set for you or an admin to approve. Start with the workflows you need now, then add more as your work grows.

One prompt, in your tool

›forge, help our team get set up

Your AI tool looks at your code and your tickets in Jira, Linear, or Notion. Forge uses what it finds to recommend workflows, with a reason for each, and suggests a real task to start on.

Nothing connected yet? Setup still runs with what your AI tool can see. Re-run it any time as your team changes.

What to expect

Sign in once. Your tool opens a browser window; new accounts are free.
Nothing runs until it's turned on. Setup proposes; you or an admin approve.
Your code stays in your AI tool. Your tool reads and changes code using its existing access. Forge supplies workflow instructions; its service does not directly access your repository.
Your rules stay in place. CLAUDE.md, .cursorrules, and your existing skills keep working exactly as they are.

Step 3 · Your first result

Try one real task.

After setup, run one of the workflows you enabled on your own work. Put your ticket in place of ENG-214.

Have a PR ready for review?

Check the change against requirements, tests, and team standards.

›forge, review the PR for ENG-214

You’ll get: structured findings, coverage gaps, and next actions.

Already built something?

Ask Forge to recap the branch you have been working on.

›forge, what did we just build?

You’ll get: a recap grounded in your changes and tests.

More ways to bring Forge into a session →

No Jira, Linear, or Notion connected? You can still start. Forge hands you the results to paste, and writes them to the ticket once you connect one through your AI tool.

Install the plugin.
Then run guided setup.