Choose hosted tools for the remote workspace, or local stdio for your desktop browser queue.
Choose the workspace before copying a configuration
MCP gives an AI client a defined set of tools. It does not, by itself, decide where your data lives or give an assistant control of your computer. ListingSail offers a hosted MCP endpoint and a local server inside the Windows companion. Choosing between them is a workflow decision: do you want a licensed hosted planning workspace, or the companion's local briefs and browser queue?
The two workspaces are separate. A product saved through the hosted connection will not automatically appear in the desktop app, and the local browser does not become remotely available just because you connected the hosted URL. Choose one deliberately for the task. If a tool shows an empty product list, first check which workspace the client is using.
Use hosted MCP for a licensed remote workspace
The hosted endpoint is https://listingsail.com/mcp. It exposes twelve tools for product briefs, directory research, campaign planning, outcome records and public link observations. Compatible clients connect over Streamable HTTP and authenticate with an active ListingSail license in a Bearer header. The connection guide provides distinct examples for Codex, Claude Code, Cursor and VS Code.
Keep the license in the private environment used by the connecting client. Copy a configuration containing an environment-variable reference, not a populated key. Different clients use different reference syntax. ListingSail does not currently provide an OAuth connector flow, so an OAuth-only setup is not an equivalent substitute. Opening the MCP URL as a normal browser page returns HTTP 405; use the client to test the protocol connection.
Use the companion when the work needs your browser
The local stdio server exposes fourteen tools, including the companion's campaign queue and local queue status. It uses the desktop workspace and protected local activation. Its configuration launches ListingSailDesktop.exe with --mcp. Copy the exact configuration from MCP & integrations inside the app so the executable and any custom data directory point to the workspace you intended.
Local browser sessions, directory credentials and mailbox configuration belong to the companion's private application data. They are not part of the public configuration example. The local queue follows the same current website permissions and worker safeguards as the GUI. It can wait for a human step and continue the same browser form. Keep the full extracted application together, including its runtime files.
Start with a read-only check, then review the plan
After connecting, ask for license_status followed by a small list_directories query. This checks entitlement and shows the catalog without publishing anything. Inspect the saved requirements and unknowns. When saving a brief through MCP, expect unapproved facts: an assistant cannot grant itself the human review, publication permission or registration permission needed for later actions.
Connecting tools is not a blanket authorization. CAPTCHA, sign-in, ownership checks, binding consent and payment still need the appropriate human action. Your AI provider's access and usage limits also remain separate from the ListingSail subscription. A clear setup keeps these decisions visible: which client, which workspace, which reviewed facts and which actions you actually want to allow.
Put the guide into practice with your own reviewed website facts.
Choose your AI connectionOriginal ListingSail product guide. Features and directory requirements can change; check current documentation and official destination rules. This guide is not a case study or a promise of traffic, rankings or publication.