Guide

Claude connector

The Claude connector links your ListingRVA AI workspace to Claude through a hosted MCP (Model Context Protocol) server. Once it is connected, you can ask Claude to read your product catalog, generate listing copy, and publish images to your store, without leaving your editor. It works with any MCP client, Claude Code, Claude Desktop, or claude.ai. This guide covers the full setup and everything the connector can do today.

Overview

MCP is the open standard Claude uses to talk to external tools. The ListingRVA AI connector is a remote MCP server hosted at mcp.listingrvaai.com. You add it once with your API key; Claude then calls it on your behalf and works only within your own workspace. The connector itself stores no keys, and each request is authorized by the key you provide.

MCP endpoint	https://mcp.listingrvaai.com/mcp
Transport	Streamable HTTP
Auth	Authorization: Bearer lor_<key>
Plan	Any paid plan (Starter and up)

Requirements

You need two things:

A ListingRVA AI account on any paid plan (Starter and up; API keys are not on the free plan).
An MCP client. This guide uses Claude Code; any MCP client that supports a remote HTTP server works the same way.

Setup in Claude Code

1. Create an API key

In ListingRVA AI, open Settings → API Keys and create a key. Copy it immediately, it is shown only once. Keys look like lor_... and carry the scopes you grant (see scopes below).

2. Add the connector to your MCP config

Add the block below to your Claude Code MCP config (your global ~/.claude.json, or a project's .mcp.json) and replace lor_YOUR_KEY with the key you just created.

{ "mcpServers": { "listingrva": { "type": "http", "url": "https://mcp.listingrvaai.com/mcp", "headers": { "Authorization": "Bearer lor_YOUR_KEY" } } } }

Your API key is a secret. Keep it out of shared repositories and screenshots. If a key leaks, revoke it in Settings → API Keys and create a new one, revoking takes effect immediately.

3. Confirm the connection

Restart Claude Code so it picks up the new server, then ask Claude something like "use listingrva to show my account". Claude will call get_account and return your plan and credit balance, that confirms the connector is working.

Other MCP clients

The endpoint is a standard remote MCP server, so any MCP-capable client can use it. Point the client at https://mcp.listingrvaai.com/mcp and send your key in the Authorization: Bearer lor_<key> header. An X-API-Key: lor_<key> header is also accepted.

Authentication & scopes

Every request is authenticated by your API key and runs inside that key's workspace. A key carries one or more scopes, and each tool needs a specific scope. Grant only what you need.

Scope	What it allows
read	Read your account, products, assets, and job status.
ai	Generate listing copy (spends credits).
write	Publish an existing image asset to a connected store.

A tool called with a key that lacks its scope returns an insufficient_scope error. Add the scope to the key (or create a new key) in Settings → API Keys.

Available tools

These are the tools the connector exposes today. Claude picks the right one from your request, you rarely name them directly.

Tool	Scope	Does
get_account	read	Plan, subscription status, and credit balance.
list_products	read	Products in your workspace, newest first.
list_assets	read	Generated images/assets, optionally filtered to one product.
generate_listing_copy	ai	Write title, bullets, description, and keywords for a product. Runs asynchronously and returns a jobId.
get_job	read	Poll a generation job by its jobId and fetch the result when it completes.
push_to_store	write	Publish an existing image asset to a connected Shopify, WooCommerce, Magento, Etsy, BigCommerce, or Amazon listing.

generate_listing_copy is asynchronous: it returns a jobId, and Claude polls get_job until the copy is ready. This is the same job pipeline as the dashboard, so the same credit cost and plan tiers apply.

Example prompts

Once connected, plain requests work. For example:

"List my ListingRVA products."
"How many credits do I have left?"
"Write Amazon listing copy for my stainless steel water bottle."
"Show the images I've generated for that product."
"Publish the latest image for that product to my Shopify store."

Data & security

Claude can only see and do what your key's scopes permit, all inside your own workspace.
The connector does not persist your API key, it authorizes each request and forwards it.
Requests are rate limited per key, so one key's activity never affects another customer.
Revoke a key any time in Settings → API Keys; it stops working immediately.

Troubleshooting

Symptom	Fix
Claude doesn't see the server	Restart Claude Code after editing the config so it reloads MCP servers.
401 / unauthorized	Check the Authorization header value is Bearer lor_<key> and the key hasn't been revoked.
insufficient_scope	The key is missing the scope that tool needs. Add it in Settings → API Keys.
"not enough credits" on copy	Generating copy spends credits. Top up or wait for the next cycle.

What's coming

Generating new product images from inside Claude is next. Today the connector reads your catalog, assets and credits, generates listing copy, and publishes existing images to your store.

Need a hand connecting?

See the connector page or reach out and we'll help you set it up.

Connector page Get your API key