ForgeOps + MCP Knowledge Base

Stop being the memory system for your AI coding agent.

ForgeOps gives your agent project memory, scoped work, handoffs and guardrails, so no session starts from zero. It comes with its own local memory, the MCP Knowledge Base.

Get ForgeOps for $197 See what's inside

One-time payment · 10 spots · 14-day refund, no questions asked

> /forge-load my-app
━━━ MY-APP SESSION LOADED ━━━
Phase: v2, checkout flow
Last session: cart totals fixed, tests pass
Next: wire the receipt email
Is this still accurate?

Every new chat starts cold.

You paste the same context in again.
Decisions stay buried in an old thread.
Scope drifts because the boundaries aren't loaded.
You end up as project manager, prompt engineer and guardrail.

ForgeOps moves that work out of your head and into files your agent reads every time.

Seven pieces that install the loop.

A workflow layer, not a prompt pack: project state, source-of-truth docs, scoped loops, handoffs and guardrails, backed by a real local memory store.

8 ForgeOps skills

forge-load, forge-scope, forge-build, forge-pr-loop and forge-close, plus align-prd, align-roadmap and the RISEN prompt builder.

The MCP Knowledge Base

A local, private memory server (SQLite, runs on your machine) that the skills query and write.

Setup, start to finish

Installation for the skills and the Knowledge Base.

Templates

Project-state and handoff templates.

An example project state

A filled-in .forge/ folder showing exactly what a governed project looks like.

The integration spec

How the skills pull memory in and write it back, documented.

Full documentation

The whole Forge method, written down.

About that knowledge base: ForgeOps uses it for project memory, but it's yours, not just the system's. Save anything you want your AI to remember, whether that's decisions, gotchas, ideas or half-formed product thoughts. It all stays local.

Five steps, every session.

Load
The agent reads the project's state and asks if it's still right.
Scope
One bounded piece of work, with what's allowed and what isn't.
Build
A build prompt grounded in your project's own files.
PR loop
Build, test, review. You approve each merge.
Close
A handoff is written, so tomorrow starts warm.

From people using it.

"I didn't know what I was doing with Claude. As sessions pile up with context, everything slows down, and starting fresh meant manually writing countless prompts trying to compile everything core to my project. ForgeOps has that built in. It makes the handoff for you, backs it up on your machine, and loading the project into a new session is all I do now. I forget what I'm doing quite often, especially after a few days. I just ask what we're working on and it lays it out."

MikeForgeOps bundle user

"A session starts by reading my two files back to me and asking if that is still right. The next day, or a different AI, it starts where I left off instead of where it guesses I left off."

MarkUses the two-file method

It's for you if

You build with Claude Code, Cursor, Codex or Windsurf.
You keep losing the plot between sessions.
You want less re-prompting, not more process.

It's not for you if

You want a magic prompt pack.
You expect perfect code with no review.
You want something that posts or ships on its own.

Why I built ForgeOps

I stopped being
the memory system.

I knew I was ready to get into agentic systems, but I didn't know how. After a long process of isolating good habits and removing bad ones, ForgeOps was born. If someone else knows the time is right to get into agents, ForgeOps is the system that gives them a real place to begin.

Get ForgeOps.

10 spots

$197 one-time

8 skills and the MCP Knowledge Base
Setup for both
Templates and an example project
Full documentation

Get ForgeOps for $197

You pay right here on this page, through Stripe. Any sales tax is worked out at checkout.

Questions before you buy.

Is this just another prompt pack?

No. It's a workflow layer: project state, source-of-truth docs, scoped loops, handoffs and guardrails, backed by a real local memory store.

Do I need to set up a database?

No. The Knowledge Base is included and sets up in three steps. No accounts, no cloud, nothing leaves your machine.

Will it make the AI code perfectly?

No. It improves continuity, scope control and handoff discipline. You stay in the loop.

Why not just use chat memory?

ForgeOps uses visible project files so state is inspectable, editable, portable, and tied to the project instead of living only in vague recall.

Will this slow down vibe coding?

Yes, at first. When you're new you tell the AI to build five features in one prompt, with no roadmap and no idea what a PRD is, and you can go very fast. With the better models you even get results. Adding structure takes time: planning, scoping, phases, versions. You make it back by not fixing and re-debugging everything a Frankenstein prompt produced. The speed you lose up front comes back as time you stop spending on cleanup.

Too advanced for me?

The whole loop is five steps: load, scope, build, pr-loop, close. Start with the included example state files. Setup instructions are included in the download.

Ready to stop starting from zero?