Tru Commerce for AI assistants, over MCP.

Before you connect

1. Have a Tru Commerce account. Sign in at app.trucommerce.ai with a work email; that is the account you will approve the connection with.
2. Run at least one scan in the app. The tools read your workspace; an empty workspace returns empty answers.
3. Use an assistant that supports remote MCP servers with OAuth. Every client below does.

Connect your assistant

Each client asks for the same two things: a name and the server URL. When you save, it opens the Tru Commerce sign-in page; check the address bar shows app.trucommerce.ai, sign in, and approve the connection.

Claude (web and desktop app)

1. Open Settings, then Connectors, then Add custom connector.
2. Name it Tru Commerce and paste https://mcp.trucommerce.ai/mcp.
3. Click Add, sign in when the window opens, and approve. The connector shows as connected.

Claude Code

claude mcp add --transport http trucommerce https://mcp.trucommerce.ai/mcp
claude mcp list

The first command opens a browser window for sign-in. The second should list trucommerce as connected. Add --scope user to make it available in every project.

ChatGPT

1. Open Settings, then Connectors. If you do not see an option to create a connector, turn on developer mode under Advanced settings first. Custom connectors need a paid ChatGPT plan.
2. Create a connector named Tru Commerce with the server URL and OAuth authentication. Sign in and approve.
3. In a new chat, enable the connector for that conversation and ask your question.

The ChatGPT apps directory also lists our published app under our former name, Asva AI. Either route reaches the same workspace data.

Cursor

Open Cursor Settings, then MCP, and add this to your mcp.json:

{
  "mcpServers": {
    "trucommerce": {
      "url": "https://mcp.trucommerce.ai/mcp"
    }
  }
}

Windsurf

In Cascade, open the plugin panel and add a custom server:

{
  "mcpServers": {
    "trucommerce": {
      "serverUrl": "https://mcp.trucommerce.ai/mcp"
    }
  }
}

Meta Muse

Muse has no settings screen for MCP servers. Meta documents custom connectors that Muse builds itself from a service’s API or CLI (Meta Help Centre, September 2026); pointing it at an MCP endpoint is not in Meta’s documentation, but it has worked in our own tests. Tell it:

Create a custom connector for Tru Commerce. It is a remote MCP server over streamable HTTP at https://mcp.trucommerce.ai/mcp.

Muse opens the Tru Commerce sign-in page in its own browser. Confirm the domain is app.trucommerce.ai before you sign in. Muse is available in the United States and Canada as of September 2026.

What to ask

Ask in plain language; the assistant picks the tool. If it answers from general knowledge instead of your data, start the message with “Use Tru Commerce to…”.

• “How are we doing on AI search this month, and what should I fix first?”
• “Which competitor gained the most Share of Voice on ChatGPT in the last 30 days?”
• “Which domains cite us most, and which ones cite our competitors instead?”
• “Show me the prompts where we are never mentioned and the answers ChatGPT gave.”
• “Which of our products show up in AI shopping answers, and on which shelf?”
• “What did the assistant search for before answering the top prompt in our category?”

The tools

Nineteen tools, all read-only. Most take an optional run to pin a scan date; the assistant resolves brand and prompt ids for you through list_brands and list_prompts.

Sign-in, tokens and your data

• Sign-in is OAuth 2.1 with PKCE. The assistant registers itself as a client, sends you to app.trucommerce.ai to approve, and receives its own token. It never sees your password.
• Access tokens last 15 minutes and refresh automatically; refresh tokens last 30 days.
• Every tool call is authorised against your account and logged against it for support and audit, as described in our privacy policy. No tool returns another customer’s data.
• The server is read-only. Changes to keywords, competitors, scans or settings happen in the app.
• To stop access, disconnect the connector in your assistant. To have a connection revoked immediately, email [email protected].

Building your own MCP server for your catalog? Start with the MCP security checklist or let MCP App Builder host it. The MCP integration page covers what we deploy over a catalog.

Troubleshooting

• The sign-in window never opens. Allow pop-ups for your assistant, or copy the URL it printed and open it yourself.
• The assistant answers without using your data. Start the message with “Use Tru Commerce to…” and name the brand.
• “Invalid token” after a few weeks. The refresh token expired. Disconnect and reconnect the connector.
• A tool says data is not available. The workspace has no scan yet, or the brand is not in it. Check the app.

Still stuck? Email [email protected] with the client you are using and the error text.