Developer · Local MCP server
AgentForge
Turn rough requests into rigorously structured prompts, for any coding agent.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.sciscale/agentforge-mcp- Version
- 0.1.4
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-05-24
- Updated
- 2026-05-24
- Publisher
- org.sciscale
- Namespace
- Namespace verified by the MCP Registry via the domain sciscale.org · how
- Website
- agentforge.sciscale.org
- Repository
- github.com/sciscale-studio/agentforge-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | agentforge-mcp | 0.1.4 | stdio |
How to connect AgentForge
AgentForge runs locally from a Node.js package published to the npm registry: agentforge-mcp version 0.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y agentforge-mcp@0.1.4. It reads these environment variables: AGENTFORGE_API_KEY (required, secret) and AGENTFORGE_API_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agentforge-mcp": {
"command": "npx",
"args": [
"-y",
"agentforge-mcp@0.1.4"
],
"env": {
"AGENTFORGE_API_KEY": "<secret>",
"AGENTFORGE_API_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AgentDriveCross-agent artifact workspace with provenance across Claude Code, Codex, Cursor, LangGraph. | Remote · HTTPLive check: ✓ handshake |
| agentegressSee which AI agent and MCP server talks to what on Windows, with a rule-based security verdict. | Local · stdio |
| agentfensterWindows GUI automation on a hidden second desktop, driven from Claude Code over MCP. | Local · stdio |
| Agentforce Action Audit13 rules on a Salesforce Agentforce topic file, before the deploy and before Article 50. | Local · stdio |
| AgentglassScan any public URL for hidden instructions aimed at AI agents (prompt injection). Free, no auth. | Remote · HTTPLive check: ✓ handshake |
| agentguardMCP policy proxy: spend caps, approvals for destructive tools, kill switch, dry-run, audit log. | Local · stdio |
| AgentguardAgentGuard - 20-tool AI safety MCP: policy preflight, risk scoring, audit logging, rate limits. | Remote · HTTPLive check: ✗ no handshake |
| agentguard - policy proxy for agent tool callsFree spend report from an agent log, no key. Hosted proxies: caps, audit export, buy calls. | Remote · HTTPLive check: ✓ handshake |