MCP
Connect AI agents to approved workspace context without broad credential exposure.
MCP
Use MCP when an AI assistant needs workspace-aware context, schema inspection, or guided setup. MCP does not replace human approval for scope, credentials, or launch readiness.
Surfaces
| Surface | Use for | Boundary |
|---|---|---|
| hosted MCP | OAuth-based AI-agent access | approved workspace scope |
| local stdio | trusted local development | local credentials and machine access |
| docs search | finding guidance | read-only context |
| OpenAPI | HTTP contract generation | implementation details |
Agent Handoff
- Give the agent the workspace goal, enabled features, and allowed change scope.
- For ecommerce work, ask the agent to run
check-feature-progressbefore handoff. - Keep Secret Key handling in trusted local or server environments.
- Ask the agent to report verification commands and changed files.
- Review workspace changes before launch.
Stop Conditions
- credential owner is unknown
- agent scope is broader than the task
- plan-blocked features are requested
- launch readiness has unresolved blockers
AI-agent access should be scoped to the workspace and task. Do not use MCP as a shortcut around credential ownership or launch review.
Next Actions
- Confirm owners in Integrations & Keys.
- Check implementation contracts in API.
- Finish with Launch Readiness.