signalforge
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@signalforgeanalyze my prompt: build me a portfolio app"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SignalForge
SignalForge is a local-first MCP prompt intent compiler. It turns vague user requests into task-specific, cost-aware prompts for Codex first, while keeping adapters for Claude Code, Cursor, ChatGPT, Kimi, and generic LLM workflows.
It is not another prompt prettifier. SignalForge detects intent, missing context, workflow shape, context waste, and likely failure modes before you spend a full model run.
What It Does
Analyzes rough prompts for task type, clarity, missing context, and waste risks.
Compiles prompts for Codex, Claude Code, Cursor, ChatGPT, Kimi, or generic clients.
Suggests split plans for large tasks instead of one expensive mega-prompt.
Provides reusable prompt patterns for common workflows.
Saves only user-approved patterns locally in
.signalforge/patterns.json.Does not save raw prompts by default.
Related MCP server: knitbrain
Install
npm install
npm run buildRun As An MCP Server
Codex:
codex mcp add signalforge -- node C:\Users\Karthikey G\OneDrive\Documents\signalforge\dist\stdio.jsClaude Desktop / Claude Code style config:
{
"mcpServers": {
"signalforge": {
"command": "node",
"args": ["C:\\Users\\Karthikey G\\OneDrive\\Documents\\signalforge\\dist\\stdio.js"]
}
}
}MCP Inspector:
npm run inspectCLI Smoke Test
npm run smokeOr run directly:
node dist/cli.js analyze "build me a portfolio app" --target codex
node dist/cli.js compile "build me a portfolio app" --target codex
node dist/cli.js compile "compare these two startup ideas" --target kimi
node dist/cli.js pattern feature_build --target codexUse With Kimi
Kimi does not need MCP support for this flow. Compile the prompt locally, then paste the output into Kimi:
node dist/cli.js compile "help me design an AI automation product" --target kimiMCP Tools
analyze_prompt: intent, clarity, missing context, waste risks, workflow.compile_prompt: ready-to-use prompt with assumptions, split plan, and cost-saving notes.get_prompt_pattern: reusable template for a use case.estimate_prompt_waste: likely failure mode and cheaper prompting route.save_pattern: store a user-approved pattern locally.list_patterns: list saved local patterns.
MCP Resources
signalforge://patternssignalforge://adapters/codexsignalforge://adapters/claude-codesignalforge://adapters/cursorsignalforge://adapters/chatgptsignalforge://adapters/kimisignalforge://adapters/genericsignalforge://history/recent
Development
npm run test
npm run build
npm run smokeThe compiler is deterministic in v1. Optional LLM refinement can be added later behind an environment flag, but the core should remain useful without any API key.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/karthikeyGoli/signalforge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server