AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
MCP verified Apache-2.0 Self-run

Forge

mcp-projforge-forge · by ProjForge

Durable, project-scoped memory and semantic retrieval for AI agents and developer tools.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add mcp-projforge-forge

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/mcp-projforge-forge)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude DesktopCursorWindsurf

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Forge? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

FORGE

Durable, project-scoped memory and semantic retrieval for AI agents and developer tools.

[](https://github.com/ProjForge/Forge/actions/workflows/ci.yml) [](LICENSE) [](https://www.postgresql.org/) [](https://nodejs.org/)

FORGE is a provider-agnostic persistence layer for durable project knowledge. It gives agents and humans one relational source of truth for memories, decisions, documents, executions and auditable context, with optional vector retrieval through pgvector.

FORGE is not an agent framework and does not call an embedding model from its core. Model providers remain replaceable external workers.

The official geometric identity and usage rules live in the [brand pack](assets/brand/BRAND_GUIDE.md).

> Project status: alpha. The schema and local Workbench are validated on > PostgreSQL 18.4 with pgvector 0.8.2; PostgreSQL 14+ is the compatibility > target. APIs may evolve before 1.0.

Why FORGE

  • Project isolation: relational and semantic reads cannot cross projects.
  • Database-enforced invariants: optimistic locking, append-only history and

managed identity rules survive application bugs.

  • Provider independence: embeddings and reranking stay outside Core.
  • Agent and human access: MCP tools and a loopback-only local Workbench use

the same Gateway contracts.

  • Reproducible evolution: transactional, checksum-aware migrations and

idempotent write contracts.

  • Verified recovery: authenticated encrypted backups restore only into an

empty database and prove migration checksums and table counts afterwards.

Components

| Package | Current version | Responsibility | | --- | ---: | --- | | schema | 0.1.3 | PostgreSQL migrations and invariant tests | | persistence-gateway | 0.1.5 | Typed transactions and domain workflows | | mcp-server | 0.1.5 | Strict stdio MCP adapter | | embedding-worker | 0.1.6 | Provider-pluggable indexing worker | | semantic-bridge | 0.1.4 | Natural-language search and optional reranking | | resilience | 0.4.0 | Encrypted logical/physical recovery, immutable replication and safe restore | | workbench | 0.2.0-rc.2 | Local human-facing web application |

Architecture

flowchart LR
    Agents["Agents / MCP clients"] --> MCP["MCP Server"]
    Humans["Browser on loopback"] --> WB["Workbench"]
    MCP --> GW["Persistence Gateway"]
    WB --> GW
    WB --> SB["Semantic Bridge"]
    SB --> GW
    Worker["Embedding Worker"] --> GW
    Worker --> Provider["External model provider"]
    SB --> Provider
    GW --> DB["PostgreSQL + optional pgvector"]
    Recovery["Resilience CLI"] --> DB
    Recovery --> Backup["Authenticated encrypted recovery package"]
    Backup --> LocalReplica["Filesystem replica"]
    Backup --> CloudReplica["S3-compatible Object Lock"]

See [Architecture](docs/ARCHITECTURE.md) and the [decision records](docs/decisions/) for boundaries and trade-offs.

Quick start for contributors

Prerequisites: Node.js 20+ and npm 10+.

For the guided Windows installation, start with the non-mutating plan in the [Windows bootstrap guide](docs/INSTALL-WINDOWS.md).

TencentDB for PostgreSQL has a dedicated, fail-closed Core compatibility gate. It remains uncertified until the [provider gate](docs/TENCENTDB-COMPATIBILITY.md) passes on an isolated instance through a private VPC runner.

git clone https://github.com/ProjForge/Forge.git
cd Forge
npm install
npm run build
npm test

The default test suite uses an embedded PostgreSQL-compatible runtime where possible and does not require credentials. Native PostgreSQL, pgvector and LM Studio validation are opt-in; see each package README:

  • [Schema and migrations](packages/schema/README.md)
  • [Persistence Gateway](packages/persistence-gateway/README.md)
  • [MCP Server](packages/mcp-server/README.md)
  • [Embedding Worker](packages/embedding-worker/README.md)
  • [Semantic Bridge](packages/semantic-bridge/README.md)
  • [Resilience](packages/resilience/README.md)
  • [Workbench](packages/workbench/README.md)

Security model

FORGE treats PostgreSQL as the source of persistent truth. The Workbench binds only to loopback, keeps database credentials out of browser state and places all writes behind Gateway validation and idempotency contracts. Never expose the local Workbench directly to a network.

Please report vulnerabilities using the process in [SECURITY.md](SECURITY.md). Official binaries follow the [code signing policy](docs/CODESIGNINGPOLICY.md). FORGE does not collect telemetry; network and local-data behavior is documented in the [privacy policy](PRIVACY.md).

Contributing

Read [CONTRIBUTING.md](CONTRIBUTING.md) before proposing changes. New behavior must preserve the invariants documented in [Architecture](docs/ARCHITECTURE.md) and include tests at the narrowest useful boundary.

License

Licensed under the [Apache License 2.0](LICENSE).

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.