forge-cpp-mcp 0.2.1__py3-none-any.whl

forge_cpp_mcp-0.2.1.dist-info/METADATA

@@ -0,0 +1,436 @@
+Metadata-Version: 2.5
+Name: forge-cpp-mcp
+Version: 0.2.1
+Summary: A safe MCP server for structured C++ project development workflows.
+Project-URL: Homepage, https://github.com/hardened-steel/ForgeMCP
+Project-URL: Repository, https://github.com/hardened-steel/ForgeMCP
+Project-URL: Issues, https://github.com/hardened-steel/ForgeMCP/issues
+Project-URL: Changelog, https://github.com/hardened-steel/ForgeMCP/releases
+Author: ForgeMCP contributors
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: mcp[cli]==2.1.1
+Requires-Dist: pydantic>=2.13
+Requires-Dist: regex>=2024.11.6
+Provides-Extra: build
+Requires-Dist: build>=1.3; extra == 'build'
+Provides-Extra: dev
+Requires-Dist: build>=1.3; extra == 'dev'
+Requires-Dist: pytest>=9.1; extra == 'dev'
+Provides-Extra: test
+Requires-Dist: pytest>=9.1; extra == 'test'
+Description-Content-Type: text/markdown
+
+# 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. Quality and
+debugger modules are 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.
+- CMake tools list operator profiles, configure projects, build targets, and run
+  CTest. Each tool has its own widget with profile filters, Fields/JSON views,
+  copying and per-test results. Command logs are available through `process_get`. CMake syntax highlighting remains deferred.
+- Tool `processes_overview` shows running and completed external development tools,
+  including exit codes and timeout interruptions. `process_get(process_id)` returns
+  one process with its ordered stdin/stdout/stderr transcript.
+- Resources `forgemcp://processes` and `forgemcp://processes/{process_id}` expose
+  Markdown snapshots of the list and one process.
+- Tool `toolsets_list` lists every discovered toolset; `toolset_get(toolset_id)` returns
+  its absolute executable paths, kinds, and versions. Both open the toolsets widget.
+- Resources `forgemcp://toolsets` and `forgemcp://toolsets/{toolset_id}` expose the
+  toolsets as markdown, querying available versions for details, with completion
+  for retained toolset IDs.
+
+The tools remain useful in clients without MCP Apps support because the Python SDK
+serializes their typed results into both text `content` and `structuredContent`.
+
+All widgets share a compact console style with a fixed 420px height and adapt to the
+host width. The move confirmation uses only two rows, source and destination.
+Long values wrap and remain selectable; overflow scrolls vertically.
+File views separate line numbers and offer a wrap toggle with horizontal scrolling.
+Search groups matching lines by collapsible file, highlights matches, expands clipped
+context on click, and keeps skipped files in a separate tab.
+Fields, local filters, copy icons and syntax-highlighted JSON show the supplied result
+without making additional tool calls. Process times are readable to seconds; JSON and
+copying preserve the original precision. A toolsets list shows summaries, while a
+`toolset_get` result shows the details returned by that call.
+
+ForgeMCP does not expose arbitrary command execution over MCP. Feature services use
+the shared process service internally; its public MCP surface is read-only.
+
+## Requirements
+
+- Python 3.13 or newer
+- Node.js `^20.19.0` or `>=22.12.0` for source builds, clean editable installs,
+  and widget development; it is not required to install or run the release wheel
+
+The server is built against MCP Python SDK `2.1.1`.
+
+## Install a release
+
+Download the `.whl` file from [GitHub Releases](https://github.com/hardened-steel/ForgeMCP/releases)
+and install it in a virtual environment:
+
+```powershell
+python -m venv .venv
+.\.venv\Scripts\python.exe -m pip install .\forge_cpp_mcp-0.2.1-py3-none-any.whl
+.\.venv\Scripts\forgemcp.exe --help
+```
+
+The wheel includes the compiled HTML widgets and icons. No npm commands or separate
+frontend deployment are needed. CMake, Ninja, compilers, and clangd are external
+tools: install the ones needed by your workflows separately.
+The distribution name is `forge-cpp-mcp`; the Python module and server command are `forgemcp`.
+
+After the package is published to PyPI, the install command can instead be:
+
+```powershell
+.\.venv\Scripts\python.exe -m pip install forge-cpp-mcp==0.2.1
+```
+
+## Setup from source
+
+```powershell
+python -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
+```
+
+## Build
+
+One command installs the locked frontend dependencies, builds every widget, and
+creates the Python wheel with its HTML and icon assets:
+
+```powershell
+.\.venv\Scripts\python.exe -m build --wheel
+```
+
+The wheel is written to `dist/`. To build both the source distribution and a wheel
+from that source distribution, use `python -m build` in the development environment.
+Generated HTML under `src/forgemcp/assets/` is build
+output; change its source under `frontend/`, never the HTML directly.
+
+## Run
+
+Run against the current directory:
+
+```powershell
+.\.venv\Scripts\forgemcp.exe
+```
+
+Pass `--workspace` only when the target differs from the server process working
+directory:
+
+```powershell
+.\.venv\Scripts\forgemcp.exe --workspace examples/cpp-acceptance-project
+```
+
+In VS Code, the `ForgeMCP: server` launch configuration is the one-button path: it
+builds the wheel first and then starts the server for this repository.
+
+All MCP traffic uses stdout. Operational logs must go to stderr.
+
+## Connect Codex or Claude Code
+
+After [installation](#install-a-release) or [source setup](#setup-from-source), copy the appropriate example into the root of the C/C++
+project you want ForgeMCP to work on:
+
+| Client | Example | Destination |
+| --- | --- | --- |
+| Codex | [`examples/mcp-clients/codex/config.toml`](examples/mcp-clients/codex/config.toml) | `.codex/config.toml` |
+| Claude Code | [`examples/mcp-clients/claude-code/.mcp.json`](examples/mcp-clients/claude-code/.mcp.json) | `.mcp.json` |
+
+In the copied file, replace both example paths with absolute paths: the first points
+to the `forgemcp.exe` installed by setup, and the `--workspace` argument points to
+the C/C++ project root. The examples use Windows paths with forward slashes, which
+work in both TOML and JSON. On macOS or Linux, point `command` to the virtual
+environment's `bin/forgemcp` instead. If either destination file already exists,
+add the `forgemcp` entry to it rather than replacing the file. Restart the client
+after editing its configuration. Check the connection with `codex mcp list` or
+`claude mcp get forgemcp`, respectively.
+
+## Workspace files and storage
+
+All file tools use string paths such as `project/src/main.cpp` and
+`storage/build/debug`. Directory tools default to `project/`; the separate tool
+argument `root` has been removed. Python consumers use the shared `WorkspacePath`
+type, which serializes as the same string. Storage defaults to `.<project-name>.forgemcp` beside the
+project. Set its location explicitly when needed:
+
+```powershell
+forgemcp --workspace C:\Projects\Example --workspace-storage D:\ForgeMCP\Example
+```
+
+Progress notifications in workspace, process, and toolchain are limited to one per second per invocation by
+default. Configure this with `--progress-interval 2.5` (seconds), or use
+`0` to disable throttling. The first notification is immediate; intervening updates
+are dropped, not queued. Tool results signal completion even when its progress
+notification is suppressed. The interval must be finite and nonnegative.
+
+Storage is created on first use. Its persistent directories survive restarts;
+each feature module manages its own directories and cleanup. The
+process service permits working directories inside either configured root. This is
+a working-directory check, not an operating-system sandbox.
+
+| Tool | Operation |
+| --- | --- |
+| `workspace_list(path="project/", depth=1, include_hidden=false)` | Directory tree; `depth=null` expands the whole tree; a file path is an error |
+| `workspace_find_files(pattern="*", path="project/")` | Recursive filename/path glob search |
+| `workspace_file_info(path)` | Creation/modification times, byte size, owner; unavailable metadata is null |
+| `workspace_read_file(path, start_line=1, end_line=null)` | UTF-8 text, with an optional inclusive line range |
+| `workspace_search(query, path="project/", regex=false, extensions=null, case_sensitive=true)` | Matching lines and skipped binary/non-UTF-8 files |
+| `workspace_write_file(path, text)` | Create or overwrite; return removed/added line counts |
+| `workspace_edit_file(path, old_text, new_text, replace_all=false)` | Exact replacement; zero or ambiguous matches fail without modifying the file |
+| `workspace_move(source, destination)` | Move a file or directory; destination must not exist |
+| `workspace_delete(path)` | Delete a file or empty directory |
+| `workspace_mkdir(path)` | Create a directory and missing parents |
+
+Text is UTF-8; writes use a sibling temporary file and `os.replace`. There are no
+revision/hash parameters. Edits preserve text outside the replacement, including
+line endings. Parents must already exist for file writes and moves.
+
+Directory trees hide dot-prefixed directories unless `include_hidden=true`;
+dot-prefixed files remain visible. Searches skip directories beginning with a dot and do not follow links. Ordinary
+`build` directories and dot-prefixed files are searchable. Explicit file reads may
+access hidden directories and in-root links. Mutations cannot traverse links;
+moving/removing a whole tree containing links is rejected. Dependent modules may
+register protected paths, which remain readable but cannot be changed through the
+workspace API. Searches intentionally have no application-level timeout, result
+limit, or pagination in this iteration.
+
+File resource templates use a single path including its project/ or storage/ prefix:
+
+```text
+forgemcp://workspace/file{/path*}
+forgemcp://workspace/raw{/path*}
+forgemcp://workspace/list{?path,depth,include_hidden}
+forgemcp://workspace/find-files{?pattern,path}
+forgemcp://workspace/file-info{?path}
+forgemcp://workspace/search{?query,path,regex,extensions,case_sensitive}
+forgemcp://workspace/results/{result_id}/{name}.json
+forgemcp://workspace/results/{result_id}/{name}.md
+```
+
+Examples: `forgemcp://workspace/file/project/src/main.cpp`,
+`forgemcp://workspace/raw/storage/build/debug/app.exe`, and
+`forgemcp://workspace/search?path=project/&query=TODO&extensions=cpp,hpp`.
+Use `depth=all` for a full resource tree and `include_hidden=true` to include
+dot-prefixed directories. Text-search extensions are comma-separated;
+an omitted parameter means any extension and `extensions=` means extensionless
+files. Encode query values using percent encoding (spaces as `%20`, not `+`);
+regex is supported. Text mirrors return the original text, raw mirrors return MCP
+binary content, and the other four resources return `text/markdown`.
+
+Dependent modules may register workspace result providers. A tool's `resources`
+object maps each contributing provider name to a descriptor with `uri` and
+`mime_type`. There is no manifest
+or `extensions_uri`. All result resources are immutable, held in memory, and
+disappear on restart.
+
+Write/edit return `resources.diff` linking to `diff.json` with URI and MIME type.
+This typed resource contains `path`, compact `changes` ranges, and `hunks` with
+context/added/removed lines, original/new numbers, exact text including line
+endings, and character `spans` in zero-based Unicode code points [start, end).
+Starts are one-based; a zero count denotes an empty range at an insertion position.
+Diff data is absent from the primary result. Widgets read the named resource
+and display changes without headers or a redundant diff label. The Highlight
+changes button toggles changed-substring highlighting next to Wrap lines; local
+search uses a separate color. JSON and Copy all retain the original tool result.
+A resource-loading failure does not change the successful file-operation outcome.
+When a CMake configuration has a compilation database and clangd in its toolset,
+Workspace reads, writes, and edits of C/C++ files also return
+`resources.clangd`. This immutable JSON contains diagnostics and semantic
+highlighting grouped by configuration. Workspace mutations synchronize retained
+clangd sessions; changing a header refreshes already opened dependent files.
+Clangd starts sessions from CMake's configuration subscription and keeps them until
+the configuration disappears, its database changes, or the server stops.
+Workspace widgets load both resources independently. The source view lets you
+select a configuration for semantic highlighting and inline diagnostic markers;
+lexical C/C++ colors also cover keywords, comments, literals, directives, and nested
+brackets. Diagnostic hover panels show messages and related locations on underlined
+ranges. Symbol type/signature hover is not yet included in Workspace snapshots.
+Diff annotations apply to new/context lines only. Resources shows the complete saved
+JSON with copying; large JSON uses plain text to keep tab switching responsive.
+JSON and Copy all preserve the original tool result.
+Moves synchronize clangd sessions without collecting a diagnostic resource.
+The standalone diagnostics widget uses severity cards with ranges and related notes;
+hover renders Markdown descriptions and highlights C/C++ signature blocks.
+Definitions, references, and workspace symbols group matches by file and show a
+saved source excerpt when a location is selected. Workspace symbols also show their
+kind and containing scope; document symbols form a collapsible document outline.
+Managed excerpts are captured with the tool result; external `root/` locations have
+no source preview because explicit external reads require confirmation.
+
+## CMake profiles
+
+`cmake_profiles` lists profiles. `cmake_configure`, `cmake_build`, and `cmake_test`
+operate on all profiles unless a nonempty `profiles` list selects a subset.
+Configuration must precede building, and building must precede testing. Profiles
+run sequentially; one failed execution does not suppress later executions.
+Each tool returns its own list of per-profile/preset results. The sole outcome
+field is `error`: null means success, otherwise it explains the failure (including
+the exit code for a failed command). Results include `process_id` for reading
+command output through `process_get`; they do not duplicate logs. Configure returns the build-directory and compilation-database paths
+when known; build returns parsed step counts when available; test returns JUnit cases.
+Full process transcripts remain in the process module; CMake results contain no
+transcript links. The default command timeout is 600 seconds per execution and
+can be overridden with the existing `ProcessTimeout` shape (`total`, `idle`).
+
+With no explicit profiles:
+
+- If `CMakePresets.json` or `CMakeUserPresets.json` exists, the automatic `presets`
+  profile runs all available configure, build, or test presets for that operation.
+  Names come from the selected CMake's `--list-presets=all`; ForgeMCP does not parse
+  preset JSON, inheritance, conditions, macros, or associations.
+- Otherwise, `Debug` and `Release` profiles use separate
+  `storage/build/cmake-Debug` and `storage/build/cmake-Release` directories.
+
+`--cmake-toolset ID_OR_NAME` selects the automatic profiles' toolset (default:
+`system`). Repeated `--cmake-profile NAME KEY=VALUE ...` replaces automatic profiles:
+
+```powershell
+forgemcp --workspace C:\Projects\Example `
+  --cmake-profile debug toolset=system configuration=Debug generator=Ninja `
+  --cmake-profile release toolset=system configuration=Release generator=Ninja
+```
+
+Profile settings are `toolset`, `configuration`, `generator`, `build-directory`,
+`c-compiler`, `cxx-compiler`, `toolchain-file`, and repeatable
+`define=CMAKE_VARIABLE=value`. Compiler names refer to tools in the selected
+toolset. Build directories and toolchain files use `project/...` or `storage/...`.
+Plain profiles default to the Ninja generator and enable compilation-database
+export. Ninja must exist in the selected toolset; there is no generator fallback.
+Without a compiler setting, CMake discovers the compiler in the toolset's
+environment. ForgeMCP does not select another toolset as a fallback.
+When the generator changes, configure completely removes the existing build
+directory and recreates it before configuring. The cache must belong to this
+project, and workspace root, protected-path, and symlink checks still apply.
+
+Native preset profiles use repeatable `configure-preset`, `build-preset`, and
+`test-preset` settings; ForgeMCP does not infer links between them:
+
+```powershell
+forgemcp --workspace C:\Projects\Example `
+  --cmake-profile native toolset=system `
+    configure-preset=ninja-debug `
+    build-preset=build-ninja-debug `
+    test-preset=test-ninja-debug
+```
+
+Preset execution delegates directories, toolchains, and environments to CMake/CTest;
+ForgeMCP neither resolves nor prevalidates `binaryDir`. A profile may supply
+`build-directory` for ordinary build/test commands when corresponding presets are
+absent. This must identify the preset's actual build directory inside project/storage.
+Such ordinary commands use the toolset environment, not a replay of configure-preset
+environment variables; use build/test presets when their inherited environment is needed.
+Preset configure settings cannot be mixed with manual generator/compiler/cache settings.
+No profile settings are read from environment variables or persisted by ForgeMCP.
+Progress messages identify the profile and current configure step, build action,
+or CTest case, with the common notification throttle. Preset generators are not
+overridden; their compilation-database settings remain controlled by the preset.
+
+The initial CMake slice does not yet include clean/project-inspection tools
+or syntax highlighting. Unit and in-process MCP tests cover profiles,
+command parsing, generator changes, result resources, and qualified paths.
+
+## Toolchain discovery
+
+Before serving requests, ForgeMCP discovers one System toolset from `PATH` and, on
+Windows, a separate toolset for every Visual Studio instance reported by the standard
+Installer `vswhere.exe`. Each VS toolset uses its own `VsDevCmd.bat` environment.
+Toolsets can be incomplete or empty. ForgeMCP does not select a current or preferred
+toolset; consumers must supply an explicit ID.
+
+Add separate user toolsets with repeated `--toolset NAME TOOL=PATH ...` options:
+
+```powershell
+forgemcp `
+  --toolset "LLVM 20" `
+    "cmake=C:\Tools\CMake\bin\cmake.exe" `
+    "clang=C:\LLVM20\bin\clang.exe" `
+    "clang++=C:\LLVM20\bin\clang++.exe" `
+    "clangd=C:\LLVM20\bin\clangd.exe" `
+  --toolset "LLVM 22" `
+    "clang++=D:\LLVM22\bin\clang++.exe" `
+    "lldb-dap=D:\LLVM22\bin\lldb-dap.exe"
+```
+
+Names must be unique, and tool names must match built-in specs. Relative paths resolve
+against the server working directory; paths inside the workspace are permitted.
+Invalid explicit paths are configuration errors and never fall back to system tools.
+User toolsets inherit the server environment. Their IDs are deterministic hashes of
+their names, so changing paths keeps an ID stable.
+
+Built-ins cover CMake, CTest, Ninja, Make, MSBuild, MSVC (`cl`), `link`, Clang,
+`clang++`, `clang-cl`, GCC, `g++`, LLD, `lld-link`, clangd, Git, LLDB-DAP, GDB, and
+`cppvsdbg`. The last adapter may be found as `OpenDebugAD7.exe` or VS Code's bundled
+`vsdbg.exe`; it has no portable version probe. An unknown or failed version probe
+leaves the discovered path available with a null version. Version methods for `cl`,
+`link`, `cppvsdbg`, and `lldb-dap` are not implemented in this iteration.
+
+Toolsets are discovered once per server lifetime; restart to discover changed
+installations. Detail tools and resources query available versions on each request,
+without caching them. Listing toolsets does not launch version probes. All probes,
+`vswhere`, and the command capturing `VsDevCmd` plus `set` remain visible in the process
+overview and retain their transcripts. Toolset resources omit environments; the
+environment capture's stdout is retained in its ordinary process transcript.
+
+## Tests
+
+Tests that need a C/C++ workspace use the shared `cpp_acceptance_project` fixture from
+`tests/conftest.py`. It copies the complete acceptance project into a fresh pytest
+temporary directory for each test, so tests can modify their workspace without
+changing repository files.
+
+## Verify
+
+```powershell
+.\.venv\Scripts\python.exe -m build --wheel
+.\.venv\Scripts\python.exe -m pytest -q
+git diff --check
+```
+
+See [docs/architecture.md](docs/architecture.md) for module boundaries and the
+registration lifecycle. Repository rules for coding agents live in [AGENTS.md](AGENTS.md).
+See [docs/releasing.md](docs/releasing.md) for distribution checks, GitHub Releases,
+and the separate final PyPI publishing step.
+
+## Reading process logs
+
+`process_get` accepts `lines`, `time`, and `max_bytes` (default 65536). With neither
+selector it reads the last 100 lines. For example:
+
+```json
+{"process_id": 42, "time": {"last": 1}, "lines": {"last": 100}, "max_bytes": 4000}
+```
+
+Each selector takes exactly one form: `{"first": N}`, `{"last": N}`, or
+`{"start": A, "end": B}`. Lines start at 1 and ranges include both endpoints.
+Time uses seconds from process start and includes start but excludes end. Last
+seconds are relative to request time while running and completion after exit.
+Time is measured when a chunk is recorded, not when each character was produced.
+
+Selection applies time, then lines within that selection, then the combined UTF-8
+text byte budget (excluding JSON/metadata). Absolute line numbers are retained.
+Tail selections keep the end when bytes run out; other selections keep the start.
+A lines selector determines direction when supplied, otherwise the time selector does.
+Partial lines are allowed, but UTF-8 characters are never split. `max_bytes=0`
+returns metadata without text. The response adds only `lines: [first, last]`, or
+null for an empty selection; each entry carries its own inclusive start/end lines.
+All streams share line numbering in observed order; entries can overlap a line.
+LF advances the line, including split CRLF; standalone CR is preserved as text.
+The retained journal and the existing process Markdown resource remain complete.

forge_cpp_mcp-0.2.1.dist-info/RECORD

@@ -0,0 +1,83 @@
+forgemcp/__init__.py,sha256=uiMHypMm70UPJbPd1G5uYU5AErRhI8JPFlGf8Yaz17o,74
+forgemcp/assets.py,sha256=5TlPNbDT76FfyjGMzg77iv1R_ksYoOiM9PxClmib6B4,1726
+forgemcp/completion.py,sha256=0VdDgllzj_sIY6eZBD0EHpZafuoNKk8l504adUmIvqA,1307
+forgemcp/markdown.py,sha256=qbYv6u6XySKBQFy-3XqoUhP9qsE1C8VSZIuSsBvKKjU,7504
+forgemcp/progress.py,sha256=eZrdT6Vyoo-1hQFC_rB2Mr2YHacLQZQ8zmkFKaTkOeY,1134
+forgemcp/server.py,sha256=VmYH6zwEf5qWZMVu5f1g0SfEcgshdKcb76BEvOGg2_0,6377
+forgemcp/assets/clangd-result.html,sha256=YnHY05eVIFV_LDfBdldlt48BMvl0PlqS0hovR5xy8qc,579159
+forgemcp/assets/cmake-build.html,sha256=-tFI7Zr-2c3jZGVZzFClGkrSnq3LY_4FQYuc08CO0X8,467314
+forgemcp/assets/cmake-configure.html,sha256=5tpslPACFphGFNfNhhegRndJiPM9syQZmoZnkDOY-0k,467338
+forgemcp/assets/cmake-profiles.html,sha256=aIjkhmzOkmQ5o7_iCKyZBY4HXHxltX2MEOCuyyyBKIU,467326
+forgemcp/assets/cmake-test.html,sha256=gncg84YpmkgW15y7eBgtvS0oAPZ82L_NJXPfEpyFMLI,467316
+forgemcp/assets/process-details.html,sha256=5iabo4LJvzJ3_z_isVg2l_mszv3Mwc9yfWClAoC3G5I,457724
+forgemcp/assets/process-overview.html,sha256=8YXPextYAy3GGnSYRQaBZZ4XgIOwb8lZNXH_KUDD6zI,470086
+forgemcp/assets/toolsets.html,sha256=MyENGvuTXI3dUEqxEn92nyS0bWIpYuxdrnfqpGC-BjI,466505
+forgemcp/assets/workspace-file.html,sha256=p1zKSlbBTjko5iWSrPKaovnnmfSJS8D8_L_XtchHxL0,594104
+forgemcp/assets/workspace-result.html,sha256=t1ZkxYB-ffjfqOMPhm-pX-yJ739Wi6GYx3Nj2m55PQc,594110
+forgemcp/assets/workspace-search.html,sha256=J2RkniuioEWyHyFz43leAb6pJWvwggixr19szECiJ_k,594110
+forgemcp/assets/workspace-tree.html,sha256=SNTv82his_o9TmJaDLuBNfL6S85EkYgKY0B-ReUuGPg,594104
+forgemcp/clangd/__init__.py,sha256=28CNWRBBzNsktJ5md1__XM859vCNa6XgtpGpvM4WL6k,49
+forgemcp/clangd/errors.py,sha256=KgAzoT1HuKZyR-PZRpD1embGDpqAO3wxQYAVqDxGh0o,909
+forgemcp/clangd/models.py,sha256=DxQ3TDUFTw1i8O3AwvIA2Tznt6-gBjTey7NRrS1Zp9Y,2366
+forgemcp/clangd/service.py,sha256=Zmyjod5jyFa3DIHik3JIJgTYMJCdl4suKoAcrkGYgmE,48324
+forgemcp/clangd/session.py,sha256=TZ3IcGYUCE3lbuhT_T6LXPV5yXSHZZbeQDztFm3G7r0,20670
+forgemcp/cmake/__init__.py,sha256=qI2hkfi4GsZj_rpa24E3M2LUnIYCbKEgVCmNDiNtFMU,43
+forgemcp/cmake/errors.py,sha256=lieFb-ADgJneQjFgkJjPTbj1UVmWE4njncl6gj4Q-IE,169
+forgemcp/cmake/profiles.py,sha256=dqmJz6RPJnUBfl8oV48ewI6KWY46J7kMTFTQcW5iB4w,3594
+forgemcp/cmake/service.py,sha256=FLbRA-Q7Z7Q4wdolgkG-jU4JkfLCTHyJyLccKxmBND8,43056
+forgemcp/icons/clangd.LICENSE,sha256=9ysSDROFQI6eOArMAgdW62uhtGHWbDKOpnMnugjX3P0,12263
+forgemcp/icons/clangd.svg,sha256=za6pqUyRhl-hnzF65DNF0Xbyim2vYv6Tp0K0zyHTf0o,1864
+forgemcp/icons/cmake.svg,sha256=76fBkKz4OUm1lbzwYYdia1KO9HWSr_u_ItyFvKetMRw,677
+forgemcp/icons/process.svg,sha256=1BoCqUwYZUYgUn6uhGPTqKOW_TZOVOa4_BfANN8rSMY,247
+forgemcp/icons/toolchain.svg,sha256=d5XaQwAl4ypgF4dJoY_6GjD2d92SEs4yIGU4DBPHKYc,254
+forgemcp/icons/workspace-edit.svg,sha256=PsWRrzX_8o7UZ8BQD0M8hVhfPZEqOYuJEGP6w_TH6dw,261
+forgemcp/icons/workspace-file.svg,sha256=hSFhrEbeca0mJJtLmZru8JhfS488jIQKLnUZf-tV2P4,268
+forgemcp/icons/workspace-search.svg,sha256=0H9kseGpppC4jY0-SWjlglH5Ionh0eEolFyKIR8BB1c,273
+forgemcp/icons/workspace.svg,sha256=Ik4CdguQnYM4N1LgEEbEfjys1kjHliax_34DnS2NeQg,186
+forgemcp/process/__init__.py,sha256=AgA_kCMjAqEYamEoJDt1r-BO7oUhxXnVeCdgMkjks6w,377
+forgemcp/process/errors.py,sha256=HKm052X3_U4BVyT6jcObRPPhEFSltJTVHMySs3oNKRg,560
+forgemcp/process/models.py,sha256=IXgxT-hkRcWCkD1Vgk-mLCjcyVfIzNEarMt9NmVWC18,4940
+forgemcp/process/service.py,sha256=RCz6WuXXVZnYm0Qfu9xoICX3dVeohuLPburt453aoXY,31158
+forgemcp/process/transcript.py,sha256=MOJjz4HuAeU1yM8rs0H8erMD1P8qcN37JLeos9ZaxLQ,4064
+forgemcp/toolchain/__init__.py,sha256=EJIuBS2kRnPawqSiGqCps86AJB-K4H2AFp1zeTfZn7E,66
+forgemcp/toolchain/discovery.py,sha256=-XN4CWMoxU9LF4tITj7P0QaLYqNW36u6Bwhp5KwQsCE,978
+forgemcp/toolchain/errors.py,sha256=DZvAdCp1QgVxA_Jy6y6p7sFWCJ4ktQ25UBRDccT_UhU,1125
+forgemcp/toolchain/loader.py,sha256=4CFQRhRR8-BqMXZ82Q5WPwQv2rlQPiswH2S4mdUglg0,1675
+forgemcp/toolchain/service.py,sha256=18TMEjd4zxI-fpfuCdwYKftYYREVk4TSSjAQAKJAW0E,8315
+forgemcp/toolchain/spec.py,sha256=4pIEAtsDocHmqk8G8wia7iX1Zwjyopg_OZsXZ1277eI,1920
+forgemcp/toolchain/providers/__init__.py,sha256=F7-o8c-sPbUohFFGtl925X_7o5-EElJ7mtCk1OYoyKM,75
+forgemcp/toolchain/providers/system.py,sha256=A1Rgwrz-7dUmSSL8UZrVRNTnrxGMo33hMB299uIXeO8,1864
+forgemcp/toolchain/providers/user.py,sha256=pC0U_EJCnc-zlv8o4mm6JEIt-ukgnWcE7fFWBBG6R0A,3138
+forgemcp/toolchain/providers/visual_studio.py,sha256=X26gfAKc63MQnq8XWAf7IDrhdupoQnSmPYhYMzrZs2U,7124
+forgemcp/toolchain/tools/__init__.py,sha256=_XfdPYomtc8WunNyhcxWZYkCP9hRhtoZZzm39rwmS0E,74
+forgemcp/toolchain/tools/clang.py,sha256=dUvq7YfPvzBbiMJRUK_fXIBdFDBSkLxkXIINIVw4-CU,2118
+forgemcp/toolchain/tools/clang_cl.py,sha256=R8WQzIH6LZPj-e-nWgwqS95tNVXAyTFY69B9iEHHNAo,2124
+forgemcp/toolchain/tools/clangd.py,sha256=W3FnjUuFq2MWpMJXN7V4A7f7OgkKL5eVmye09nl6pLA,10138
+forgemcp/toolchain/tools/clangxx.py,sha256=sc09QwIyZjLtnOPbnbbtn6hOtaposqGroSMwTO7nNps,2122
+forgemcp/toolchain/tools/cmake.py,sha256=4kWahLsGBMH3eoTZHJwbDhToh3pHKKpDuEe0IMR9mKs,9509
+forgemcp/toolchain/tools/cppvsdbg.py,sha256=58d_-OBeZ_H8d6NCFg32j_HJNFFVBFTKXIxDSl5ihyg,626
+forgemcp/toolchain/tools/ctest.py,sha256=B9isOnI8XXFsgG918mNqyXlTWtx3JKXIR4eNicj_jHY,7351
+forgemcp/toolchain/tools/gcc.py,sha256=X_3st8xzSHzh1BpBcT8wtSUcjuRCemqR8bZzkN3g0Q0,2133
+forgemcp/toolchain/tools/gdb.py,sha256=OUo_OdlSF7DgVCtE1DdfmN-ecwui_Q1DcR8Y4TerL4g,2140
+forgemcp/toolchain/tools/git.py,sha256=QtLGLGVIlohcaXzKAaGQplQe6djiEkh2nTWk_yrb9bg,2119
+forgemcp/toolchain/tools/gxx.py,sha256=YsQPZuKMSESBnf3sgUnjIQ_W9exMUF0OM8VUvyIEVUg,2133
+forgemcp/toolchain/tools/link.py,sha256=3YxI-R3GT-EhReJjQiMDSYCpY6iE9Z62jbM6iCqT77U,616
+forgemcp/toolchain/tools/lld.py,sha256=dJHiEvYKsGnCoz7Q2n9xbzaYy8v7qX7P5y7ZTSF_x60,2119
+forgemcp/toolchain/tools/lld_link.py,sha256=fxRcB6FykdBqgp4M5hPLVODssavfVlOYC5XKm-NYAdY,2112
+forgemcp/toolchain/tools/lldb_dap.py,sha256=WfY_WfS0zHDTaTOqtkIwtezRmi-0rCoFCQZQoUUqq5U,626
+forgemcp/toolchain/tools/make.py,sha256=sp1cO22jnt2DfCCRj_sCHPb-XqNgg4CuqS7-y2L4V2Y,2115
+forgemcp/toolchain/tools/msbuild.py,sha256=t2E8ckLm9b6lJag4-joUPMYBdeMLxWg8brui2jWjhT4,2132
+forgemcp/toolchain/tools/msvc.py,sha256=qn4fo8Hj4372Ga69LzdR4uKmO4UGEAIiT4TqArdtADQ,614
+forgemcp/toolchain/tools/ninja.py,sha256=ljdfgKnVvnV-cZJgd6lVgk6ck0zfp-iWl_odkPn6QBU,2119
+forgemcp/workspace/__init__.py,sha256=llKNs_pzQXauEE2D5EoITjJMfXrKrkDXes5q898WWec,107
+forgemcp/workspace/diff.py,sha256=SNRdBG5I04DU3cY09ilFZT1cZf7nguHR8Z8jDMbT5Xk,5755
+forgemcp/workspace/errors.py,sha256=rWUN_VGcc83UsmT6xFw_zf3PjxaJ6ESTzKVChD5Oy8g,121
+forgemcp/workspace/metadata.py,sha256=tyCuU3QT8y0g1-_DHQoB9eaaPMKqDER-sEB_HICaqA0,2437
+forgemcp/workspace/path.py,sha256=oM3ZqqsltwzRWtmrot5wCIUG8ioRR0xetnvVM-s9GiA,2729
+forgemcp/workspace/providers.py,sha256=-kgB2xVh3Ofal_WDO9wDf-2VfCjVjLxfmAWCaa_K5BA,615
+forgemcp/workspace/service.py,sha256=Vkv_0EPHOZYLJ9SNaykxtmnV0Mo5ZOItwWCW8rHFyrM,69442
+forge_cpp_mcp-0.2.1.dist-info/METADATA,sha256=M698TuWLP9rSjmn7i7-MGgLxU85qHaZsWZ-x5Uu8ngE,23261
+forge_cpp_mcp-0.2.1.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
+forge_cpp_mcp-0.2.1.dist-info/entry_points.txt,sha256=X3lvpCOLmNNRl5SUIs2Py6jNR_ySNbIHo43OkeJTwjk,50
+forge_cpp_mcp-0.2.1.dist-info/licenses/LICENSE,sha256=LmXV0zKMUYEP9wGMetoup7zgKNN_29LFO_Jey5VR5so,1071
+forge_cpp_mcp-0.2.1.dist-info/RECORD,,

forge_cpp_mcp-0.2.1.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.32.4
+Root-Is-Purelib: true
+Tag: py3-none-any

forge_cpp_mcp-0.2.1.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+forgemcp = forgemcp.server:main

forge_cpp_mcp-0.2.1.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 hardened-steel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

forgemcp/__init__.py

@@ -0,0 +1,5 @@
+"""ForgeMCP package."""
+
+__all__ = ["__version__"]
+
+__version__ = "0.2.1"