Apps and MCP Tools

Use this guide to understand the platform's app suites, MCP (Model Context Protocol) integration, and how to connect AI tools to your handle.

All browser-first operator surfaces now run on https://app.{PUBLIC_DOMAIN}. Use /apps/ as the current catalog/front door for product workflows, /creator/* for creator workflows, and /smartwork/launch/{projectId} when a Smartwork project is opened from the first-party launcher.

When to use

• You want to manage campaigns, deployments, or analytics from an app interface.
• You want to connect an AI assistant or LLM to your handle via MCP.
• You need to register custom function bindings for tool-based integrations.

For a single end-to-end runbook across schema setup, analytics checks, and function-binding data delivery, use Platform-Wide Feature Exploration Lab.

Browser app surfaces

The platform exposes two browser app collections on the unified app.{PUBLIC_DOMAIN} host: creator workflows under /creator/* and the /apps/ catalog for product and operations workflows.

Creator workflows

These routes are direct browser entry points under https://app.{PUBLIC_DOMAIN}/creator/*.

Access: JWT authentication required (CREATOR role or above).

Apps catalog and product workflows

The canonical product entry point is https://app.{PUBLIC_DOMAIN}/apps/. Each module opens from the browse catalog at /apps/browse/{appId}/playground; older shortcut paths such as /apps/attribution are preserved only as compatibility redirects inside the SPA.

Smartwork browser runtime

Smartwork is part of the same unified browser host, but it is launched separately from the /apps/ catalog.

MCP integration

The platform exposes a Model Context Protocol (MCP) server that allows AI assistants and LLMs to interact with one handle programmatically.

What is MCP?

MCP is a protocol that lets AI tools (like Claude, ChatGPT, or custom agents) call structured functions on your behalf. Instead of navigating the UI or writing API calls, you describe what you want in natural language and the AI uses MCP tools to execute it.

Available MCP tools

The MCP server exposes live MCP tool families for links, analytics, routing, knowledge, runtimes, deployments, and related operations.

Connecting an AI assistant

1. Create one connector per handle.
2. Point the connector to https://{handle}.mcp.10x.in/mcp or https://api.10x.in/mcp/{handle}/mcp.
3. Complete the OAuth redirect and approve the scopes the connector needs.
4. Let the shared bootstrap workflow recover auth, validate scopes, and resume the requested handle workflow.
5. Let the hosted MCP transport use the OAuth-issued bridge credential. Do not paste raw usernames or passwords.

For detailed ChatGPT/OpenAI setup (auth handshake, scopes, and verification), follow ChatGPT MCP Setup.

MCP hosting

The MCP server can be accessed in multiple ways:

Sessions are managed via Redis with a configurable TTL (default 30 minutes). Each session is scoped to a handle and authenticated with the OAuth-issued bridge bearer for that connector.

Why MCP stays on platform domains

Platform MCP hosting currently depends on:

• platform-managed wildcard DNS and certificates for per-handle MCP subdomains
• environment-owned OAuth discovery metadata and protected-resource metadata
• environment-owned host parsing for handle resolution and session routing

Supporting MCP on customer-managed custom domains would require additional wildcard delegation, certificate lifecycle management, and OAuth metadata hosting for every customer domain. That is not supported today.

WebMCP browser tools

The platform also provides 6 built-in browser tools that work in the page context:

Function bindings

Function bindings let you register custom tool definitions that are exposed through the MCP server and public API.

Creating a function binding

POST /v2/handles/{handle}/function-bindings

{
  "bindingKey": "product-lookup",
  "template": "proxy_request",
  "enabled": true,
  "config": {
    "toolname": "Product Lookup",
    "tooldescription": "Look up product details by SKU"
  }
}

Requirements:

• PRO plan or above (growth_tools feature gate).
• Binding key must match ^[a-z0-9][a-z0-9_-]{1,63}$.
• Template must be one of: proxy_request, webhook_forward, form_submit, signed_redirect.

Listing function bindings

GET /v2/public/handles/{handle}/function-bindings

Returns all enabled bindings with their tool name and description. This is the endpoint MCP clients use to discover available functions.

Invoking a binding at the edge

GET|POST /_edge/fn/{handle}/{bindingKey}

Use this path to invoke a binding runtime after creation/discovery. For proxy_request, the runtime returns an echo-style payload with method/path/query details.

UI path

1. Open https://app.{PUBLIC_DOMAIN}.
2. Navigate to your handle settings.
3. Open the Integrations tab.
4. Configure function bindings or view MCP connection details.
5. Use /apps/ from the main navigation to browse product workflows, or open the creator modules under /creator/*.
6. Open /smartwork/launch/{projectId} when you need the first-party Smartwork launcher for a project.

Required auth

• CREATOR-level JWT for app suite access.
• OAuth connector grant with appropriate scopes for MCP tool usage.
• pages.read/pages.write scopes for campaign-structure MCP tools.
• PRO plan required for function bindings (growth_tools gate).
• PAT remains valid for non-MCP automation routes where explicitly documented.

Common errors

Related:

• Platform-Wide Feature Exploration Lab
• API Tokens and Automations
• Plans, Quotas, and Feature Gates
• Chain Signals and Prefetch
• Glossary