JTLGO Commerce MCP

One MCP connection for public commerce and account work.

Public connector is for open product search, China rate quotes, and tracking. Account connector adds OAuth and authenticated account tools for account summary, work items, and support ticket creation.

Public connector

No sign-in needed to discover tools. Good for general sourcing and logistics calls.

https://jtlgo.com/api/mcp

Account connector

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

https://jtlgo.com/api/mcp/account

Open account connector

2 access modes

Public connector and account connector

6 public tools

Search, quote, track, detail, handoff, config

10 tools in account mode

All 6 public tools plus 4 scoped account tools

Account connector setup

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

Account endpoint https://jtlgo.com/api/mcp/account

Configure in your client

OAuth behavior The client uses the account connector URL. The protected-resource metadata points to the authorization server. After sign-in, the client retries MCP calls with a scoped Bearer token.

Resource metadata https://jtlgo.com/.well-known/oauth-protected-resource/api/mcp/account/

Authorization server https://api.jtlgo.com/sourcing/mcp/oauth

Scopes account:read, work_items:read, support:write

get_account_summary Read the signed-in account summary and customer-level state exposed to the connector.

list_customer_work_items List customer work items that still need attention.

get_customer_work_item Open one customer work item in detail for the assistant.

create_support_ticket Create a scoped support ticket when the assistant must escalate.

Choose your client.

Use the public URL for anonymous-only work. Use the account URL as the single connector when you want all public tools plus scoped account tools.

Codex / ChatGPT

Use the public URL for anonymous-only work. Use the account URL for one connector containing all public and scoped account tools.

Paste this connector URL

No sign-in needed to discover tools. Good for general sourcing and logistics calls.

https://jtlgo.com/api/mcp

Use the same endpoint in your client connector field or config file.

Public connector

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp"
    }
  }
}

TOML config

[mcp_servers.jtlgo-commerce]
url = "https://jtlgo.com/api/mcp"

Paste this connector URL

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

https://jtlgo.com/api/mcp/account

Use the same endpoint in your client connector field or config file.

Account connector · account:read, work_items:read, support:write

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp/account"
    }
  }
}

TOML config

[mcp_servers.jtlgo-commerce]
url = "https://jtlgo.com/api/mcp/account"

Claude

Claude can use public for anonymous discovery, or account as one combined connector with OAuth and all tools.

Paste this connector URL

No sign-in needed to discover tools. Good for general sourcing and logistics calls.

https://jtlgo.com/api/mcp

Use the same endpoint in your client connector field or config file.

Public connector

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp"
    }
  }
}

Paste this connector URL

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

https://jtlgo.com/api/mcp/account

Use the same endpoint in your client connector field or config file.

Account connector · account:read, work_items:read, support:write

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp/account"
    }
  }
}

VS Code / Cursor

Editor agents can choose the anonymous public connector or the combined account connector per workspace.

Paste this connector URL

No sign-in needed to discover tools. Good for general sourcing and logistics calls.

https://jtlgo.com/api/mcp

Use the same endpoint in your client connector field or config file.

Public connector

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp"
    }
  }
}

Paste this connector URL

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

https://jtlgo.com/api/mcp/account

Use the same endpoint in your client connector field or config file.

Account connector · account:read, work_items:read, support:write

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp/account"
    }
  }
}

Any MCP Client

If the client supports Streamable HTTP or hosted MCP, paste either the public connector or the account connector directly.

Paste this connector URL

No sign-in needed to discover tools. Good for general sourcing and logistics calls.

https://jtlgo.com/api/mcp

Use the same endpoint in your client connector field or config file.

Public connector

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp"
    }
  }
}

Paste this connector URL

Use this single endpoint for all public tools and scoped customer tools. The MCP client starts OAuth only when account access is required; this browser page never handles the token.

https://jtlgo.com/api/mcp/account

Use the same endpoint in your client connector field or config file.

Account connector · account:read, work_items:read, support:write

{
  "mcpServers": {
    "jtlgo-commerce": {
      "url": "https://jtlgo.com/api/mcp/account"
    }
  }
}

Public tool matrix

These are the six public tools exposed by the public connector today.

Tool	Use it for	Typical input	Returns
search_products	Catalog discovery	keyword, site, limit	Safe product candidates
quote_shipping_rates	China route estimate	countryCode, weight, dimensions	Route and billing-weight options
track_shipment	Order and parcel tracking	tracking number or list	Latest timeline and exception hint
get_product_detail	Single item inspection	id or product URL	Safe product detail fields
human_handoff	Manual fallback	language, reason	Email and WhatsApp support path
get_mcp_config	Setup verification	none	Connector metadata and tool list

What this page no longer asks you to do

OK No ZIP package download path.
OK No local package installation path.
OK No secret-credential instructions.
OK No anonymous auth/me probe from the page.

Before you leave this page

Why does the test use POST?

The MCP endpoint now enforces POST JSON-RPC. GET metadata is intentionally rejected with 405.

When do I use the account connector?

Use it when the assistant should open OAuth and access customer-specific tools under account:read, work_items:read, or support:write.

Do I need both URLs?

No. Choose public for anonymous-only use, or account as one connector containing all public and scoped account tools.