mocop
Browse · Docs · Guide · Analyze

MemBrowse

MCP server by MemBrowse · mcp

MemBrowse tracks the memory footprint (flash, RAM and other regions) of firmware and other ELF builds for every commit. These tools are read-only. Sizes are bytes. Reviewing a pull request: get_commit_summary with the PR's head commit SHA shows every target's change against the PR's base branch, with the largest section and file changes and, for targets with benchmark metrics, how each metric moved; then compare_builds with level='symbols' and the same head SHA on a target that grew shows which symbols grew. Auditing memory: list_targets (how full each region is) -> get_memory_history (the commits that changed it, with their deltas) -> compare_builds with level='symbols' on a commit that grew it, or between two releases; list_symbols shows what takes the space. Benchmark metrics (cycle counts, timings, scores CI attaches to commits) are separate from memory: get_metric_history lists a target's benchmarked commits with each metric's change, to find the commit that moved one; then get_c…

Endpoint: https://api.membrowse.com/mcp

Verification: observed. Source: crawl.

Capabilities (8)

  • list_projects
  • list_targets
  • get_commit_summary
  • get_memory_history
  • get_metric_history
  • compare_builds
  • list_symbols
  • export_symbols
About · Contact · Privacy