> For the complete documentation index, see [llms.txt](https://help.cubelet.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cubelet.ai/platform-and-integration/mcp-servers.md).

# MCP servers

*The Model Context Protocol servers that make up the cubelet.ai platform, and how tool responsibility is split across them.*

cubelet.ai is served by a federated fleet of MCP servers rather than one monolith. Each server is reachable at its own `/mcp` path over the MCP **Streamable HTTP** transport — point your client at the endpoint URL directly.

## The fleet

| Server                                       | Endpoint                                                          | Purpose                                                                                                                                                                                                                                                                              |
| -------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| GRID42 Cubelet Manufacturing (`manufacture`) | `https://manufacture.cubelet.ai/mcp`                              | The platform's primary server, and the one to point at by default. Generic Cubelet content, concept navigation, cross-domain simulation, **and** the CMMC, ISACA, AI Governance and GRC domain tool suites. See the manufacture — Cubelet Manufacturing page for the full tool list. |
| CMMC Catalyst                                | `https://cmmc-catalyst.cubelet.ai/mcp`                            | CMMC knowledge-repo server — CMMC reference and consulting tools, scoped to that domain only.                                                                                                                                                                                        |
| CMMC Assessment                              | `https://cmmc-assessment.cubelet.ai/mcp`                          | CMMC consulting-delivery server.                                                                                                                                                                                                                                                     |
| CMMC Cubelets Platform                       | `https://cmmc.cubelet.ai/mcp`                                     | Earlier CMMC cubelets server. Consolidating into CMMC Catalyst — do not build new integrations against it.                                                                                                                                                                           |
| ISACA Cubelets Platform                      | `https://isaca-governance-simulator.euler-center.workers.dev/mcp` | ISACA Tri-Cert (CISA/CISM/CRISC/CDPSE) domain server — ISACA reference and reporting tools, scoped to that domain only.                                                                                                                                                              |
| The Scaffold PJRC                            | `https://scaffold-mcp.euler-center.workers.dev/mcp`               | The gap-diagnostic server. Runs the PJRC (Pattern, Judgment, Relationship, Creative) assessment that produces a learner's Gap profile — the first stage of the Scaffold → Pursuit → Passport journey.                                                                                |

## How the fleet is split

{% hint style="success" %}
**Changed August 2026.** The CMMC, ISACA, AI Governance and GRC tool suites used to be reachable *only* on their dedicated workers. They are now also registered on `manufacture`, which carries the same entitlement bindings, so the gates resolve identically either way. If you built an integration that points at a dedicated worker for these tools, it still works — nothing was removed. New integrations should point at `manufacture`.
{% endhint %}

* **`manufacture`** is the generalist and now the superset for almost everything:
  * Cubelet retrieval (`cubelet_get`, `cubelet_list`, `cubelet_search`), the cross-domain `catalog_cubelets` registry view, and concept navigation (`concept_navigate`, `concept_graph`, `concept_translate`).
  * The simulation suites for ISACA, AI Governance, and CMMC.
  * **CMMC** reference, consulting and coaching: `cmmc_domain_get`, `cmmc_practice_get` / `_list` / `_search`, `cmmc_gap_analysis`, `cmmc_sprs_score`, `cmmc_poam_generate`, `cmmc_evidence_guide`, `cmmc_readiness_report`, `cmmc_coach_explain` / `_recommend`, `cmmc_tier_capabilities` / `_compare`.
  * **AI Governance** reference and reporting: `ai_gov_framework_ref`, `ai_gov_traiga_ref`, `ai_gov_tools_ref`, `ai_gov_report`.
  * **ISACA** reference and reporting: `gjf_get_priority_stack`, `gjf_get_lens`, `isaca_report_export`.
  * **GRC**: `stix_coverage`, `thesaurus_negotiate`.
* **Dedicated domain workers** still serve their own domain's tools at their own endpoints, for integrations already pointed there and for domain-scoped deployments.
* **VulnOps is the exception.** All `vulnops_*` tools remain on the VulnOps worker only, and are **not** served by `manufacture`. Point at the VulnOps worker for those.

Calling a tool a server doesn't register returns a method-not-found error rather than a fallback, so confirm the endpoint serves what your tool scope lists. The authoritative answer for any server is its own `tools/list` response — see the API reference.

Every tool call across the fleet requires authentication. See the Auth & access page.