
Json Repair
io.github.CedricKoumaPublished by GitHub account CedricKoumav0.1.0Updated Oct 24, 2026
MCP server (stdio): repair broken/malformed JSON via the AgentForge API
Overview
Lets an assistant repair broken or malformed JSON by sending it to the AgentForge API through an MCP server.
- What you can do
- This MCP server exposes a JSON repair capability: an assistant passes malformed or broken JSON and the server forwards it to the AgentForge API, which returns repaired JSON. It can run as a local stdio process from the npm package agentforge-json-repair-mcp, or connect to a remote AgentForge gateway endpoint. The manifest does not list individual tools, so the exact tool names and parameters are not documented here.
- When to use it
- Useful when an assistant regularly handles JSON that may be truncated, malformed, or otherwise invalid and needs a way to recover a usable structure instead of failing. It is a narrow single-purpose helper, so it is only worth adding if JSON repair is a recurring need in your workflow.
- Requirements
- Either a local Node.js runtime to run the npm package agentforge-json-repair-mcp over stdio, or network access to the remote AgentForge gateway endpoint. An APIM subscription key is required, supplied through the Ocp-Apim-Subscription-Key header or the AGENTFORGE_API_KEY environment variable; AGENTFORGE_BASE_URL optionally sets the gateway base URL.
Installation
In SourceWeft
- Open Json Repair in the dashboard and add it to a workspace.
- Connect Ocp-Apim-Subscription-Key credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.CedricKouma%2Fjson-repair/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"json-repair": {
"type": "http",
"url": "https://apim-agentforge-6lfm33.azure-api.net/json-repair/mcp",
"headers": {
"Ocp-Apim-Subscription-Key": "<YOUR_API_KEY>"
}
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.