KnownFix MCP server
Commit Oct 19, 2026Provides developer fixes, technical services, and workflow skills through an MCP bridge to resolve technical errors and manage software tasks.
Also known as b-hash88/knownfix-cli, knownfix
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 19, 2026
- License
- —
What is KnownFix MCP?
KnownFix provides developer fixes, technical services, and workflow skills through an MCP bridge to resolve technical errors and manage software tasks.
Summary generated from the project's README
About KnownFix MCP server
Resolving technical errors and managing software tasks through an MCP bridge is what knownfix-cli enables for developers. This server provides access to six free workflow skills, three browser-local tools, and ten scoped technical services. Users can connect via a remote streamable HTTP endpoint to various clients including Claude Code, Codex, Cursor, VS Code, and Claude Desktop. The setup process involves using specific configuration commands that print settings for the user to merge into their existing client files.
Developers can interact with the service using commands like search to find solutions for specific errors or get_overview to view the full public catalog. While search and free workflows require no account or API key, certain technical services like the Verified Repo Fix or SaaS Security Exposure Review involve specific costs and manual authorization. For local processing, the package includes offline commands like inspect-response and retry-plan that handle JSON files up to 200,000 bytes without making network calls or collecting telemetry.
What you can do with it
- 1Troubleshoot specific technical errorsA developer can search the catalog for a solution to a precise error message.
- 2Verify connection and workflow readinessUsers can test the connection by requesting a specific free skill to confirm the tool is working.
- 3Inspect JSON tool responses locallyDevelopers can validate the structure of a tool response using offline commands.
- 4Request professional repository repairsUsers can opt for a paid service to have a repository fixed within a set timeframe.
Written from the project's README. Every use case is checked against a quote from it.
How to install KnownFix MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall KnownFix MCP in Claude Code
$ claude mcp add knownfix-cli -- npx -y knownfixInstall KnownFix MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"knownfix-cli": {
"command": "npx",
"args": [
"-y",
"knownfix"
]
}
}
}Install KnownFix MCP in VS Code
.vscode/mcp.json
{
"servers": {
"knownfix-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"knownfix"
]
}
}
}Install KnownFix MCP in VS Code CLI
$ code --add-mcp '{"name":"knownfix-cli","type":"stdio","command":"npx","args":["-y","knownfix"]}'Install KnownFix MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"knownfix-cli": {
"command": "npx",
"args": [
"-y",
"knownfix"
]
}
}
}Install KnownFix MCP in Codex
$ codex mcp add knownfix-cli -- npx -y knownfixInstall KnownFix MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.knownfix-cli] command = "npx" args = ["-y", "knownfix"]
Install KnownFix MCP in Gemini CLI
$ gemini mcp add -s user knownfix-cli npx -- -y knownfixInstall KnownFix MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"knownfix-cli": {
"command": "npx",
"args": [
"-y",
"knownfix"
]
}
}
}README
View on GitHubKnownFix
Developer fixes, six free workflow skills, three browser-local tools and ten scoped technical services. The live overview is the current inventory; search/free workflows need no account or API key.
Connect
Remote Streamable HTTP: https://knownfix-backend-28.b-hash88.deno.net/mcp
npx knownfix@0.4.0 config claude-code
npx knownfix@0.4.0 config codex
npx knownfix@0.4.0 config cursor
npx knownfix@0.4.0 config vscode
npx knownfix@0.4.0 config claude-desktop
These print configuration only; they never install a client or change its files.
Claude Code uses its HTTP CLI command, Codex uses TOML, Cursor/VS Code use their
own JSON formats, and the Claude Desktop example uses a version-pinned stdio
bridge. Merge entries without replacing existing settings. bridge starts a
local MCP tools proxy to the remote endpoint; Node.js 18+ and the package's MCP
SDK dependency are required. Review downloaded packages before running them.
The connection kit includes
client references, supported install links and first-use checks. Configuration
saved, tools discovered and successful tool use are different states. After
discovery, ask the client to call get_free_skill with
{"id":"api-response-triage"}. Confirm a non-error result with the full workflow
and acceptance checklist. Do not buy, create orders or send private input as a
connection test. Use get_overview for the complete public catalog.
Offline commands
After installing this package, these commands make no network calls:
knownfix inspect-response response.json
knownfix retry-plan retry.json
Use a regular UTF-8 JSON file or - for piped stdin, maximum 200,000 bytes.
JSON output goes to stdout: exit 0 = local check/model completed, 2 = invalid
input/usage, 1 = unreadable input. No telemetry, input execution or automatic
file writes. The response inspector omits payloads, IDs and server error text;
valid envelope structure is not proof of tool success. Retry output contains
validated settings and a serial failed-attempt model, never a webhook request.
See toolkit examples and limits.
Running through npx may download the package before execution; use an installed
copy or the dependency-free repository commands for offline processing.
Install the six free skills
Standard skills/<name>/SKILL.md directories include the full workflows,
synthetic exercises, acceptance criteria and standalone helpers where relevant.
They are CC-BY-4.0, attributed to KnownFix; helper code is MIT. To review and
install with the third-party Skills CLI:
npx skills add b-hash88/knownfix --list
npx skills add b-hash88/knownfix
Choose client/scope interactively, or copy reviewed skill directories into your client's documented location. This installer downloads content and has its own network/privacy behavior. The local helper commands themselves have no telemetry.
Search and paid services
npx knownfix@0.4.0 tools
npx knownfix@0.4.0 search "your exact error"
search --json returns the complete result, including private signed offers
when applicable. Keep that output private. Search does not purchase anything.
Payment/redemption requires the owner's explicit authorization; never infer it
from installation or an agent's discovery request.
The ten-service catalog includes Verified Repo Fix ($149 USDC / 3 business days, payment only on verified delivery), Webhook Reliability Review ($179 / 3 days), SaaS Security Exposure Review ($299 / 5 days, written target/method/window authorization before testing), and Microsite Launch ($299 / 5 days, scope/content/assets approval and manual payment before work). Read the exact scope and delivery-clock conditions on each service page. Manual-approval services do not use automated checkout. No guarantee of findings, traffic, ranking or revenue.
Books is owner-only, not public sales proof. knownfix books explains this
without requesting statistics. Never put an owner credential in MCP settings.
Development
npm test runs CLI contracts against local fixtures. The storefront's
scripts/export-cli-toolkit.mjs exports generated skills, helper modules and
client formats into this checkout, keeping them aligned with the browser tools.
No npm install/publish hooks execute input or collect telemetry.
KnownFix MCP questions
How do I add KnownFix MCP to Claude Code?
Run claude mcp add knownfix-cli -- npx -y knownfix in your terminal. Add --scope user to make it available in every project.
How do I add KnownFix MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Do I need an account or API key to use the free workflows?
No, search and free workflows do not require an account or an API key.
How can I test if the connection is working?
After discovery, you can ask the client to call get_free_skill with the ID 'api-response-triage' to confirm a non-error result.
Does the CLI collect telemetry or write files automatically?
The offline commands do not use telemetry, execute input, or perform automatic file writes.
Can I use the offline commands without a network connection?
Yes, the inspect-response and retry-plan commands make no network calls.