Hosted Tools & Skills Invocation

Use this guide when you need to decide how to invoke a handle's hosted tools and skills. It connects three user-facing surfaces in one place:

• ChatGPT/OpenAI MCP for natural-language tool use
• the hosted browser workflow under Integrations -> MCP & Tools for review and exposure control
• the Chrome extension for live page-context execution on mapped domains

This page is intentionally conceptual plus procedural. It helps you choose the right surface and start using it, then links out to the setup and reference pages when you need deeper detail.

What this is for

In public 10x product terms, a hosted tool or skill is a reusable capability attached to one handle. End users do not need to think about internal runtime details. In practice, the capability can appear as:

• an MCP tool that reads or updates handle data
• a binding-backed action exposed through hosted MCP
• a reusable prompt or read-only resource surfaced by MCP Builder
• a browser-side action or experiment executed through the Chrome extension

This guide explains how those capabilities show up to end users and how to choose the right invocation path for the job.

If your job is to create, update, configure, publish, or delete a handle-hosted skill through the control plane, use JWT Skill Management. Hosted skill management uses a signed-in 10x JWT; PAT and OAuth are still used only where their invocation or connector guides document them.

Who this is for

• Handle owners and operators deciding how to invoke AI-connected capabilities
• Teams onboarding ChatGPT/OpenAI or another MCP client to one handle
• Users who need to compare hosted MCP with browser-first workflows and page-context tooling
• Marketers or growth teams validating live experiments through the Chrome extension

How end users can invoke hosted tools and skills

When to use each surface

Use ChatGPT/OpenAI MCP when you want a conversational interface that can read structured data, execute supported actions, and combine tools in one session.

Use the hosted browser workflow when you need to confirm exactly what a handle exposes before you connect an AI client. This is the best place to review tool visibility, binding exposure, custom prompts, and read-only resources.

Use the Chrome extension when the job depends on the live page itself. If you need to inject, preview, or verify on-page experiments, personalization, or page-load behavior on a mapped domain, the extension is the right surface.

If the job starts with review and ends with execution, use more than one surface:

1. Review the exposed capabilities in MCP Builder
2. Invoke handle-level tasks through ChatGPT/OpenAI MCP
3. Use the Chrome extension only for live page-context validation

Invocation walkthroughs

ChatGPT/OpenAI MCP

Use this path when you want to ask for work in natural language and let the hosted MCP tool surface handle the structured calls.

1. Confirm the handle and endpoint

   Make sure you know which handle you want to operate on. The canonical production MCP URL is https://{handle}.mcp.10x.in/mcp.

2. Complete OAuth connector setup

   Connect the handle using the OAuth flow described in ChatGPT MCP Setup. Approve the scopes needed for the tools you plan to use.

3. Start with a plain-language task

   Ask for the task directly, for example:

   • "List my recent deployments and preview the latest one."
   • "Create a short link for /launch and point it at my checkout."
   • "Show me which knowledge tools are available for this handle."

4. Refine with the returned tool results

   Continue in natural language. ChatGPT/OpenAI can use the hosted tool surface, prompts, and read-only resources that are available to that handle.

Hosted MCP/browser workflow

Use this path when you need to review, validate, or shape what a handle exposes before someone invokes it from an AI client.

1. Open the control plane

   Go to https://app.10x.in, select the handle you want to inspect, and open Integrations -> MCP & Tools.

2. Confirm the hosted connector endpoint

   Review the visible MCP URL for that handle and make sure it matches the environment and handle you expect.

3. Inspect MCP Builder

   Use MCP Builder to review:

   • visible tools
   • visible resources
   • visible prompts
   • exposed function bindings

4. Refresh before sharing or testing

   Run the builder refresh and preview refresh actions before you hand the hosted surface to a teammate or reconnect a client.

5. Hand off to the execution surface

   Once the surface looks correct, move to the actual execution surface you need:

   • ChatGPT/OpenAI MCP for conversational invocation
   • the Chrome extension for live page-context execution
   • reference validation in MCP Tools Reference when you need the concrete tool catalog

Chrome extension

Use this path when you need the capability to run inside the browser on a mapped domain.

1. Install and authenticate

   Install the 10x Chrome extension and sign in with JWT or PAT as described in Chrome Extension.

2. Open the mapped domain

   Visit the page where you want to run or verify the behavior. The extension resolves the mapped domain to the correct handle.

3. Confirm the extension is active

   Check the extension badge and popup to verify the domain is connected and the extension is enabled for that site.

4. Run or verify the page-context behavior

   Use the extension when you need live-page results such as:

   • page-load banners
   • exit-intent popups
   • CTA swaps
   • personalization variants on a real page

5. Reload after auth or config changes

   If you just signed in or changed rules, reload the page so the extension can re-evaluate the live context.

Example end-user prompts and actions

Good fit for ChatGPT/OpenAI MCP

• "List all live links for this handle and flag anything unhealthy."
• "Preview the latest site deployment and summarize what changed."
• "Show me the visible MCP tools and prompts for this handle."
• "Create a redirect for /sale and point it to my spring checkout."

Good fit for the hosted browser workflow

• "Confirm that this handle exposes the knowledge query tools before we onboard support."
• "Check whether this binding is public, authenticated MCP only, or hidden."
• "Refresh the MCP Builder preview and verify that the prompt we added is visible."
• "Review which resources and prompts a teammate will see before we connect ChatGPT."

Good fit for the Chrome extension

• "Open the mapped storefront and verify the exit-intent popup appears."
• "Visit the landing page and confirm the US mobile variant is selected."
• "Temporarily disable the extension on this domain while we debug the page."
• "Reload the page and confirm the welcome banner appears on page_load."

Troubleshooting and limits

Related guides

• ChatGPT MCP Setup
• Apps and MCP Tools
• Provider-Backed MCP Bindings
• MCP Builder and Hosted Tools
• JWT Skill Management
• MCP Tools Reference
• Chrome Extension
• Chrome Extension — Marketer Setup
• API Tokens and Automations