A safe MCP server for structured C++ project development workflows.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"forge-cpp-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ForgeMCP ForgeMCP is a Python MCP server for structured C and C++ development workflows. The repository contains workspace, process, toolchain, and initial CMake services. Clangd tools provide read-only analysis across CMake configurations with a shared result widget. External file reads ask for confirmation through MCP elicitation. The debugger uses LLDB-DAP for native program control and dump inspection; Quality remains planned. ## Current MCP surface - Workspace tools browse directory trees, find files, read UTF-8 text and file metadata, search literal text or regex, write/edit/move/delete files, and create directories. Each tool reports progress and has a packaged MCP App and icon. - Workspace resources mirror UTF-8 text and raw bytes, and expose directory trees, file lists, metadata, and search results as Markdown. Resource parameters have completions for qualified paths, extensions, depth, and boolean options. - Clangd tools list available configurations and provide diagnostics, hover, definitions, references, document symbols, and workspace symbols. Empty configuration selections use all available contexts. - No prompts are currently registered. - Debugger tools launch native programs, attach to local PIDs, and open user-mode dumps through an explicitly selected LLDB-DAP toolset. They inspect threads, stacks, variables, modules, exceptions, memory, and instructions with typed results. - Git tools inspect and modify the repository rooted at the workspace: status, diffs, history, blame, branches/tags/remotes, staging, commits, restore, stash, fetch/pull/push, merge/rebase/cherry-pick/revert, and conflict stages and continuation. Every tool has typed data, plain text, a shared Git App, and process provenance. - CMake tools list operator profiles, configure projects, build targets, and run CTest. `cmake_run_test` directly runs a project/storage test executable with literal command-line arguments. Each tool has its own widget with F…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.