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 endpoint https://jtlgo.com/api/mcp

Running MCP handshake…

Protocol: —
Tools: —
Latency: —

Compare the two connectors

Choose the right access mode first.

The product split is not “hosted URL vs config file”. The real choice is whether the client should use public tools only or launch OAuth for account tools.

Start here

Public connector

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

6 tools · no sign-in · read-only

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.

10 tools · OAuth only when account data is needed

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

Both URLs serve the same 6 public tools. Add the account URL only when the assistant has to read or write account data — it is one connector, not two.

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.

Paste this connector URL

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

https://jtlgo.com/api/mcp

JSON config

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

{
  "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

JSON config

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

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

TOML config

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

Paste this connector URL

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

https://jtlgo.com/api/mcp

JSON config

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

{
  "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

JSON config

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

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

Paste this connector URL

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

https://jtlgo.com/api/mcp

JSON config

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

{
  "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

JSON config

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

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

Paste this connector URL

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

https://jtlgo.com/api/mcp

JSON config

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

{
  "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

JSON config

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

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

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.

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

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.

Protected resource metadata

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

Authenticated account tools

These four tools appear only after the client completes OAuth.

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.

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

Authenticated account tools

Read the background

Three explainers on why agent-mediated buying is arriving, which sourcing work it removes, and how freight tools are wired.

Agent-to-agent commerce in 2026

The MCP, A2A, AP2 and ACP stack, what each layer solves, and what the forecasts actually count.

Read

What an AI procurement agent can and cannot do

Four pain points automation removes, and five China-sourcing barriers it does not.

Read

MCP server for freight quotes and tracking

Which tools a logistics connector should expose, how quoting differs by mode, and how to connect one.

Read

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.

Public verification flow POST initialize → notification initialized → tools/list. Then call get_mcp_config or search_products.

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.