UC-18: Skills Runtime and MCP Integration
Role-gated control-plane steps are intentionally excluded from this public guide; use support escalation when those operations are required. Shared company context: Gharart.com Company Context Need operator help? Escalate through Troubleshooting and Support with request IDs and repro artifacts.
Developer Outcome
Ship skills runtime and mcp integration for Gharart.com with reproducible API steps, operational limits, and clear debugging playbooks.
Prerequisites
- A valid handle and environment access for Gharart.com.
- JWT credentials plus OAuth connector grant with required scopes for this use case.
- Access to logs, support escalation endpoints, and test workspace.
Gharart Scenario
AI merchandising assistant via WebMCP.
Persona: Applied AI engineer
Business goal: Expose approved skill runtimes so Gharart assistants can query context and trigger safe actions.
Step-by-Step Flow (UI + API)
- Open the relevant Gharart workflow in the dashboard and confirm actor role access.
- Execute route calls in sequence for this use case and capture response IDs.
- Validate expected state in UI and API after each step before moving forward.
- Record artifacts (request ID, run ID, deployment ID, slug, or token) for support handoff.
Primary API Routes
| Method | Path |
|---|---|
| GET | /_edge/fn/{handle}/{bindingKey} |
| GET | /_edge/fn/{handle}/{bindingKey}/{proxy+} |
| GET | /_edge/mcp/{handle}/{target} |
| GET | /_edge/mcp/{handle}/{target}/{proxy+} |
| GET | /mcp/{handle}/{target} |
| GET | /mcp/{handle}/{target}/{proxy+} |
| GET | /v2/handles/{handle}/runtime/instances |
| GET | https://{handle}.mcp.10x.in/mcp |
| GET | https://api.10x.in/mcp/{handle}/mcp |
| POST | /_edge/fn/{handle}/{bindingKey} |
| POST | /_edge/fn/{handle}/{bindingKey}/{proxy+} |
| POST | /_edge/mcp/{handle}/{target} |
Primary MCP Tools
| Tool | Purpose |
|---|---|
pages_list | List page inventory by status before campaign-structure edits |
campaign_structure_get | Fetch campaign detail schema JSON for a campaign |
campaign_structure_upsert | Write/update campaign detail schema and page metadata |
campaign_structure_publish | Publish campaign detail page with login gate (FREE_WITH_LOGIN) |
Limits and Quotas
- Respect per-route throttles and daily write limits before bulk operations.
- Use idempotency-safe retries for write endpoints to avoid duplicate business actions.
- Schedule high-volume workflows outside peak campaign windows where possible.
Where This Breaks
- mcp route returns not_found due target mismatch
- skill publish succeeds but runtime instance remains stale
- edge function binding invocation blocked by content policy
How Gharart Debugs It
- List runtime instances and verify expected skill version
- Probe hosted MCP and compatibility MCP URLs with the same payload
- Run
campaign_structure_geton the target campaign to confirm schema availability - Validate function binding key and allowed content-type
Escalation
Use end-user escalation path:
- Submit
POST /v2/support/report. - Include
summary,details, and when availablehandle,sessionId,requestId,reproArtifact.
Audience boundaries:
POST /v2/operator/escalationsis an internal operator workflow and not an end-user escalation action.POST /v2/public/content-reportis for public abuse moderation reports, not product incident escalation.