Bambu Printer MCP vs Codebase Memory MCP

A side-by-side look at the Bambu Printer MCP and Codebase Memory MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Bambu Printer MCP logoBambu Printer MCPIndustrial & IoT · Local subprocess (stdio)Control Bambu Lab printers, slice models, manage AMS filament, and connect Blender over your LAN.69GreatAuth: api key requiredCodebase Memory MCP logoCodebase Memory MCPKnowledge & Memory · Local subprocess (stdio)Code-intelligence engine that indexes a repo into a persistent knowledge graph — functions, classes, call chains, HTTP routes, cross-service links. 159 languages via tree-sitter + Hybrid LSP, sub-ms structural queries, 99% fewer tokens than grep. Single static binary, zero dependencies, 100% local. npx codebase-memory-mcp73GreatAuth: no auth required

Verdict: choose Bambu Printer MCP for industrial & iot work as a local process; choose Codebase Memory MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Bambu Printer MCP logoChoose Bambu Printer MCP when

  • You need dedicated capabilities in the Industrial & IoT domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: PRINTER_HOST, BAMBU_MODEL, BAMBU_SERIAL, BAMBU_TOKEN.
  • You want tools like get_printer_status, get_printer_filaments, resolve_3mf_ams_slots.
Explore Bambu Printer MCP

Codebase Memory MCP logoChoose Codebase Memory MCP when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like index_repository, search_graph, query_graph.
Explore Codebase Memory MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecBambu Printer MCP logoBambu Printer MCPCodebase Memory MCP logoCodebase Memory MCP
CategoryIndustrial & IoTKnowledge & Memory
Quality signal69/100 · Great73/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingFreeFree
Required env varsPRINTER_HOSTBAMBU_MODELBAMBU_SERIALBAMBU_TOKENNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars22347,236
Directory activity 3 views 0 installs 0 upvotes 8 views 1 installs 1 upvotes
Tools4617

Tools & capabilities

Bambu Printer MCP tools 46

  • get_printer_statusGet the current status of the Bambu Lab printer
  • get_printer_filamentsGet the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, resolved slicer profile paths, match confidence, and recommended load_filaments when the printer model is known.
  • resolve_3mf_ams_slotsInspect a sliced 3MF and match its tray_info_idx filament requirements against the live AMS inventory. Does not upload or start a print.
  • list_3mf_plate_objectsList object IDs from a sliced 3MF plate. Use these IDs with skip_objects during a running print.
  • extend_stl_baseExtend the base of an STL file by a specified amount
  • scale_stlScale an STL file by specified factors
  • rotate_stlRotate an STL file by specified angles (degrees)
  • get_stl_infoGet detailed information about an STL file (bounding box, face count, dimensions)
  • list_templatesList saved slicing templates from the local template registry directory.
  • save_templateCopy a 3MF, JSON, or config file into the local template registry and register it under a template name.
  • get_slice_settingsInspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything.
  • slice_with_templateSlice an STL or 3MF using a named template from the local registry. This is a higher-level wrapper around slice_stl for template-based workflows.
  • +34 more on the listing page

Codebase Memory MCP tools 17

  • index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.
  • search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.
  • query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.
  • trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.
  • get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.
  • get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.
  • get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.
  • compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.
  • get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.
  • search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.
  • list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.
  • delete_projectDelete a project from the index
  • +5 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Bambu Printer MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "bambu-printer-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "bambu-printer-mcp"
      ],
      "env": {
        "PRINTER_HOST": "YOUR_PRINTER_HOST_HERE",
        "BAMBU_MODEL": "YOUR_BAMBU_MODEL_HERE",
        "BAMBU_SERIAL": "YOUR_BAMBU_SERIAL_HERE",
        "BAMBU_TOKEN": "YOUR_BAMBU_TOKEN_HERE"
      }
    }
  }
}

Codebase Memory MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Frequently asked questions

Bambu Printer MCP is categorized under Industrial & IoT and uses a local stdio subprocess. Codebase Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Bambu Printer MCP for industrial & iot work and Codebase Memory MCP for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Bambu Printer MCP is listed as free. Auth: api key required. Codebase Memory MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add bambu-printer-mcp and deusdata-codebase-memory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Bambu Printer MCP has a quality signal of 69/100 (Great) with 3 views, 0 installs and 223 GitHub stars. Codebase Memory MCP has 73/100 (Great) with 8 views, 1 installs and 47,236 GitHub stars.