--- title: "AAG MCP @ Connector Onboarding" slug: onboarding-mcp-connector section: Developer Onboarding status: stable description: "A guided way for new contributors to explore the Globus ecosystem, architecture, integrations, and operating model through grounded questions and answers." last-updated: 2026-10-07 --- # AAG MCP @ Connector Onboarding A guided way for new contributors to explore the Globus ecosystem, architecture, integrations, and operating model through grounded questions and answers. ## Purpose The AAG MCP @ connector is a core onboarding tool for new Globus contributors. It provides a guided way to explore the Globus ecosystem, architecture, integrations, workflows, and operating model through grounded questions and answers. The connector is not intended to replace documentation. Instead, it makes the existing documentation more accessible by allowing new team members to ask questions conversationally and discover how systems, processes, and architectural decisions fit together. Rather than relying solely on tribal knowledge, historical meeting notes, or scattered documentation, new contributors can use the connector to build ecosystem understanding while onboarding. Examples of useful onboarding questions include: - How do HubSpot and Globus work together? - What is the difference between a Program and an Operational Cycle? - What role does n8n play in the architecture? - Which system owns applicant communications? - What is the Globus SDK? - How do the Applicant, Host, and Recruiting Partner portals interact with Globus? This onboarding approach reflects the team’s goal that new contributors should be able to explore not only what the system does, but also why certain architectural and product decisions were made. ## Connector Setup During onboarding, all technical contributors should be granted access to the AAG MCP @ connector within ChatGPT. Open ChatGPT Settings. / Navigate to Apps. / Search for AAG MCP @. / Connect the application. / Authenticate using the company Microsoft account through Entra. / Start a new chat. / Explicitly select AAG MCP @ as the active source before asking Globus-specific questions. > **Select the connector as the active source** > > The connector must be selected as the active source. If it is not selected, ChatGPT may respond using general knowledge rather than Globus ecosystem knowledge. ## What the Connector Should Explain The connector should provide onboarding support across the major areas of the Globus ecosystem. | Area | Knowledge Available | | --- | --- | | Business Model | Hosts, applicants, recruiting partners, programs, placements, support workflows. | | Legacy Context | Why Globus is replacing Hanover and the architectural limitations being addressed. | | Core Data Model | Programs, Operational Cycles, workflows, applicants, hosts, placements. | | Portal Architecture | Applicant Portal, Host Portal, Recruiting Partner Portal. | | Integration Model | HubSpot, n8n, NetSuite, SEVIS, SDKs, MCPs, Data Lake. | | Workflow Model | Workflow Studio, enrollment workflows, lifecycle states, workflow versioning. | | Development Process | Replit environments, GitHub branches, Asana tickets, acceptance criteria. | | AI-Assisted Delivery | ChatGPT, Manus, MCPs, connectors, and AI-supported development workflows. | | Known Documentation Drift | Areas where implementation and documentation may not yet fully align. | ## Understanding HubSpot and Globus One of the most important onboarding topics is understanding system ownership. At a high level: HubSpot owns - Lead capture - Marketing funnels - Pre-qualification - CRM activities - Applicant communications - Early-stage prospect management Globus owns - Qualified applicant records - Applications - Operational workflows - Placement processing - Program participation lifecycle - Operational execution n8n - Event orchestration - System-to-system integrations - Workflow automation - Data synchronization Globus SDK - Standardized access to Globus services - Shared interfaces used by portals and applications - Consistent integration patterns across the ecosystem The connector should help explain not only the ownership boundaries but also how information moves between systems through onboarding links, events, workflows, and integration pipelines. ## Recommended First Questions New contributors should begin onboarding by asking questions such as: - Give me a practical overview of the Globus ecosystem. - How do HubSpot and Globus work together? - What problems is Globus solving compared to Hanover? - Explain Programs, Seasons, and Operational Cycles. - What is n8n responsible for, and what should it not be used for? - What are the primary portals connected to Globus? - What is the Globus SDK, and how do portals use it? - What should I know before picking up a Globus development ticket? - What documentation is known to be stale or drifting from implementation? These questions provide a useful foundation before working on features, integrations, workflows, or operational tooling. ## Expected Connector Behavior When responding to onboarding questions, the connector should: ## Documentation Drift & Verification > **The connector is a learning aid, not an unquestionable source of truth** > > Some ecosystem documentation may lag behind implementation. Treat connector answers as a starting point and verify before making changes. Known areas of terminology and architectural drift may include: - Program vs Season terminology - Operational Cycle terminology - Operational Cohort terminology - Legacy architecture diagrams - Historical process documentation When information appears inconsistent, contributors should verify against: - The current Globus environment - The active GitHub branch - The relevant Asana ticket - The latest product requirements - The responsible product or technical owner ## Onboarding Success Criteria By the end of onboarding, contributors should be able to independently answer: > **The onboarding question** > > Where does this fit within the Globus ecosystem, which system owns it, what documentation explains it, and what implementation details must be verified before making a change? The AAG MCP @ connector serves as a living knowledge layer that helps developers, product managers, operations users, and future contributors answer those questions consistently — accelerating onboarding and reducing dependence on tribal knowledge.