| Term | Meaning |
|---|---|
| Approved mapping | A mapping you reviewed and accepted |
| Brownfield path | Connector generation from a source inventory when catalogue data is insufficient |
| Catalogue-only progress | Approved mappings, routes, and transformation metadata in Connector Studio without a local connector project tree |
| Catalogue path | Connector generation from approved Connector Studio mappings and transformations through get_connector_scaffold_plan |
| Connector | Your integration build. The interface also calls it a project. |
| Coverage | The share of source operations that have mappings |
cs_context | Session rebind payload from create_project or init (context_id, project_id, names). Save it as cs-context.json. It is not the connector catalogue. |
| Decomposition | The process that breaks a specification into endpoints, schemas, and properties |
| Draft mapping | An AI suggestion you haven’t approved yet |
| Endpoint mapping | A match between a source operation and a target operation |
| Human gate | A review that only you can complete. On MCP, you read a data://pending_* resource and call a decide_* tool. Connector Studio never skips a human gate. |
| Mapping | A link between a source field or endpoint and a target field or endpoint |
| Materialization | Writing Grand Central-standard connector files through get_connector_scaffold_plan or host-driven brownfield generation |
| MCP session | The connection between your IDE and the MCP server. After you call init, the session is bound to one project. |
| Requester | The organization that consumes the API in a connector project |
| Responder | The organization that provides the API in a connector project |
| Route | The Camel flow for one operation: where the call starts, how you call the vendor, where you transform the body, and related steps |
| Route Builder | The Connector Studio surface for scaffolding, editing, and exporting routes |
| Route Designer | The visual canvas and palette where you edit a single route |
| Route template | A reusable route pattern learned from analyzed connectors in GitHub |
| Scaffold plan | The standard Grand Central bundle of files that get_connector_scaffold_plan returns |
| Schema mapping | A match between a source field and a target field, inside one operation. The interface labels this work Property Mappings, and the run_schema_mapping tool produces it on MCP. |
| Session file | cs-context.json, used for MCP session binding only |
| Specification | A machine-readable description of an API, such as an OpenAPI or Web Services Description Language (WSDL) file |
| Target | The canonical Grand Central platform API specification |
| Vendor | The organization whose external API you integrate with |
| Widget-less review | Default IDE path: read data://pending_*, decide in chat, call decide_* only after you instruct the assistant |
Reference
Connector Studio glossary
Terms used in Connector Studio and connector projects.
The following table describes the terms that appear throughout the Connector Studio documentation.