MCP
Connect AI agents to approved workspace context without broad credential exposure.
MCP
Use MCP when a hosted, shell-less AI assistant needs workspace-aware context or schema inspection. Shell-capable coding agents should use the CLI; hosted MCP is a single HTTP/OAuth surface for Console-backed discovery tools: get-collection-schema, get-tenant-context, and check-feature-progress. The local stdio transport was retired. MCP has no collection CRUD or commerce tools; use the CLI for shell agents and the SDK for application runtimes. MCP does not replace human approval for scope, credentials, or launch readiness.
get-collection-schema may include active custom-field structure for
customers and products under optional collection.customFields: machine
keys, types, required markers, select storage values, and the customData
storage path. It does not return operator labels or stored customer/product
values, and it does not expand MCP permissions.
Surfaces
| Surface | Use for | Boundary |
|---|---|---|
| hosted MCP | OAuth-based hosted-client access | context, schema, and feature-progress discovery |
| Agent CLI | shell-capable agents (01 agent) | local credentials, machine-stable I/O |
| API / SDK | application runtimes and server-side writes | secret-key/server credentials |
| 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.
Hosted connection
Use https://mcp.01.software/mcp with the client's supported HTTP/OAuth flow. There is no local stdio package to install. Connection and tool availability require the intended deployment plus authorized workspace access; a documentation build does not establish that access. If OAuth or discovery is unavailable, report that failure rather than substituting a Secret Key in the client.
Next Actions
- Confirm owners in Integrations & Keys.
- Use CLI when the client can run shell commands.
- Check implementation contracts in API.
- Finish with Launch Readiness.