forgein›MCP Server
Model Context Protocol

Your context as
a live protocol.

The forgein MCP server exposes your memory files as resources and prompts. Any MCP-compatible tool — Cursor, Windsurf, Zed, Claude Desktop — connects directly, no files to paste.

Get API token →MCP spec ↗
JSON-RPC 2.0 · Stateless·Auto-discoverable via /.well-known/mcp
POST /api/adapters/mcp
// prompts/get — returns full context// as a pre-built user message {  "jsonrpc": "2.0",  "method": "prompts/get",  "params": {    "name": "forgein-context",    "arguments": {      "projectPath": "-Users-alice-api"    }  }} // Response: your full context// as messages[0].content.text { "result": { "messages": [   { "role": "user", "content": {    "type": "text",    "text": "## Work Context\n..."  }} ]} }
Auto-discovery

Tools find the server
without manual config.

The forgein API publishes a /.well-known/mcp discovery endpoint. MCP clients that support it can pick up the server URL and auth instructions automatically.

GET /.well-known/mcp
api.forgein.ai
{  "mcpServers": {    "forgein": {      "url": "…/api/adapters/mcp",      "authentication": {        "type": "Bearer"      }    }  }}
~/.cursor/mcp.json
~/.cursor/mcp.json
{  "mcpServers": {    "forgein": {      "url": "…/api/adapters/mcp",      "headers": {        "Authorization":          "Bearer fg_..."      }    }  }}
Why MCP + forgein

Live context. No maintenance.
Any compatible tool.

File-based adapters require a paste step when context changes. MCP removes it — tools pull from the source directly.

01 — PROTOCOL
Context injection, standardized

MCP is an open protocol that lets any AI tool consume structured context from a server. Instead of pasting files manually, your tools pull live resources and prompts directly from the forgein MCP server.

02 — DISCOVERY
Tools find the server automatically

The forgein API publishes a `/.well-known/mcp` endpoint. MCP-compatible tools that support auto-discovery can pick up the server URL, auth instructions, and capabilities without any manual config.

03 — LIVE
No copy-paste. Always current.

Every time a tool calls `resources/read`, it gets your current context — not a snapshot you exported last week. Update a memory file and the next tool session sees it immediately.

JSON-RPC methods

Full MCP surface.
Protocol version 2024-11-05.

The forgein MCP server implements resources, prompts, and the standard lifecycle. All via stateless HTTP POST with Bearer auth.

MethodWhat it returns
⊞initializeHandshake — declares protocol version and available capabilities.
◈resources/listReturns your memory files as resources with `forgein://context/<name>/<file>` URIs.
◆resources/readFetches the full content of a specific memory file.
⌘prompts/listLists the `forgein-context` prompt.
⊙prompts/getReturns your full context as a pre-built user message — ready to inject into any system prompt.
○pingHealth check. Returns `{}` if the server is reachable.

All requests are authenticated via Authorization: Bearer fg_.... The MCP endpoint is stateless — no WebSocket, no session management.

Setup

Four steps.
Then context is always live.

No ongoing maintenance once connected. Update memory files in forgein — every tool session sees the change automatically.

01
Create account + token
Sign up at app.forgein.ai. Create an API token under Dashboard → API Tokens. Token starts with `fg_`.
02
Add to your MCP client
Point your tool at `https://api.forgein.ai/api/adapters/mcp`. Pass your token as a Bearer header or use the auto-discovery config.
03
Configure project scope
Pass `projectPath` in `prompts/get` params to include project-specific notes alongside your personal context.
04
Keep memory up to date
Edit memory files in the dashboard or via the forgein CLI. Every update is live — no re-authentication, no re-configuration.
One context. Every tool.

File adapters when you need them.
MCP when you want it live.

The same forgein context flows to every tool. Use the file-based adapters for tools that don't support MCP, and the MCP server for those that do.

⚡Claude Code
Full memory sync, skills, team sharing, /forgein CLI.
💬ChatGPT
Generated Custom Instructions — paste into ChatGPT settings.
⌥GitHub Copilot
.github/copilot-instructions.md managed across repos.
◆Gemini
Generated system prompt for Gems — paste into Gem config.
⊗Cursor
.cursorrules generated from your context — paste to any repo.
⊞Windsurf
.windsurfrules generated from your context — paste to any repo.
⬡MCP ServerYOU ARE HERE
JSON-RPC 2.0 server — any MCP-compatible tool connects natively.
Pricing

Free forever for individuals.
Pro when you need to scale.

The MCP server, work context, and memory sync are all free. Pro adds Home + Family contexts, unlimited projects, and team sharing.

Free
$0 / forever

Full MCP server access and memory sync for individual developers.

  • ✓MCP server access (all methods)
  • ✓Work context — unlimited files
  • ✓resources/list + resources/read
  • ✓prompts/get (forgein-context)
  • ✓1 API token
  • —Home + Family contexts
  • —Team memory sharing
Create free account →
ProPOPULAR
$4.99 / month

Remove the limits. All contexts, unlimited projects, team sync.

  • ✓Everything in Free
  • ✓Home + Family context via MCP
  • ✓Unlimited memory projects + files
  • ✓Team memory sync
  • ✓10 API tokens
  • ✓Private skill registry
  • ✓Priority support
Get started →

Context as a protocol.
Every tool, no configuration.

Free forever. Works with any MCP-compatible client.

Create free account →MCP docs ↗