ListingSail
YOUR ASSISTANT. YOUR NEXT HORIZON.

Your AI.
Ready to launch.

Bring ListingSail into the place you already work. Choose your AI, copy its settings and give your next launch a clear direction.

Choose your AI

Active ListingSail license required · Your own AI access

Codex ↗
Claude ✳
Cursor ⌁
ONE CONNECTED WORKSPACE

A little connection.
A bigger possibility.

license_statuslist_directories
MCP / LICENSED ACCESS→
REMOTE MCP ENDPOINThttps://listingsail.com/mcp
Streamable HTTPBearer license key12 tools · hosted workspace
MAKE YOURSELF AT HOME

Choose your AI.

A connection guide for your client.
Your license stays in your private settings.

↗Codex✳Claude Code⌁Cursor◇VS Code▦Claude Desktop / local
REMOTE / CODEX

Your launch desk.
Inside Codex.

  1. Privately set LISTINGSAIL_LICENSE_KEY in the environment used by Codex. Use your ListingSail license, not an OpenAI API key.
  2. Merge this block into ~/.codex/config.toml, preserving your existing servers.
  3. Restart the client, then check the connection with codex mcp list or /mcp.

The configuration names an environment variable. It contains no license value.

Official Codex MCP guide ↗
CONFIG.TOML
[mcp_servers.listingsail]
url = "https://listingsail.com/mcp"
bearer_token_env_var = "LISTINGSAIL_LICENSE_KEY"
Prefer the CLI?codex mcp add listingsail --url https://listingsail.com/mcp --bearer-token-env-var LISTINGSAIL_LICENSE_KEY
REMOTE / CLAUDE CODE

Keep the conversation.
Add a new capability.

  1. Privately set LISTINGSAIL_LICENSE_KEY in the environment that launches Claude Code.
  2. Merge this server into your project’s .mcp.json. Leave the environment placeholder exactly as shown.
  3. Restart Claude Code, review the project-server prompt and use /mcp to check its status.

Claude Code expands ${LISTINGSAIL_LICENSE_KEY} when it loads the configuration. Do not paste the actual value into this page or a chat.

Official Claude Code MCP guide ↗
.MCP.JSON
{
  "mcpServers": {
    "listingsail": {
      "type": "http",
      "url": "https://listingsail.com/mcp",
      "headers": {
        "Authorization": "Bearer ${LISTINGSAIL_LICENSE_KEY}"
      }
    }
  }
}
Merge this example with your existing mcpServers object.
REMOTE / CURSOR

A familiar editor.
A fresh destination.

  1. Privately set LISTINGSAIL_LICENSE_KEY in Cursor’s environment, then restart Cursor.
  2. Use the install link to review this server in Cursor, or merge the example into ~/.cursor/mcp.json.
  3. Open Customize → MCPs and check that ListingSail is enabled and connected.
Add to Cursor

The install link contains only the public URL and an environment placeholder. Cursor asks you to review the setup.

Official Cursor MCP guide ↗
MCP.JSON / CURSOR
{
  "mcpServers": {
    "listingsail": {
      "url": "https://listingsail.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:LISTINGSAIL_LICENSE_KEY}"
      }
    }
  }
}
Cursor’s ${env:NAME} syntax differs from Claude Code’s syntax.
REMOTE / VS CODE

Give your workspace
a launch companion.

  1. Privately set LISTINGSAIL_LICENSE_KEY in the environment used by VS Code. Restart the app afterward.
  2. Review the install link, or merge this example into your workspace’s .vscode/mcp.json.
  3. Run MCP: List Servers, start ListingSail and enable its tools in your agent session.
Add to VS Code

This example uses VS Code’s servers format. Other Copilot runtimes can use a different format; check the official configuration reference.

Official VS Code MCP reference ↗
.VSCODE/MCP.JSON
{
  "servers": {
    "listingsail": {
      "type": "http",
      "url": "https://listingsail.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:LISTINGSAIL_LICENSE_KEY}"
      }
    }
  }
}
For a remote editor session, the variable must be available on the host making the MCP connection.
LOCAL / WINDOWS COMPANION

Your browser.
Your computer. Your AI.

  1. Install the Windows companion for your Windows user, open ListingSail and use Paste key to activate your license. Installed copies use ListingSail.exe.
  2. Open its MCP & integrations panel. Copy the configuration with your actual executable and data paths.
  3. For Claude Desktop, open Settings → Developer → Edit Config. Merge the server and fully restart Claude Desktop.

This local connection exposes 14 tools, including the desktop browser queue. It uses your local workspace and protected activation. It does not synchronize with the separate hosted workspace.

Official local-server setup guide ↗
INSTALLED COPY / EXAMPLE PATH
{
  "mcpServers": {
    "listingsail-local": {
      "command": "C:\\Users\\YourName\\AppData\\Local\\Programs\\ListingSail\\ListingSail.exe",
      "args": ["--mcp"]
    }
  }
}
Replace YourName and this default example path with your actual installed EXE path. The website cannot know your Windows path. Use the exact app-generated configuration for a custom installation or workspace.
Using the portable ZIP instead?

Download the portable ZIP, extract the complete archive and keep _internal beside ListingSailDesktop.exe. Activate inside that copy, then use its actual extracted path. Portable copies require manual updates.

PORTABLE COPY / EXAMPLE PATH
{
  "mcpServers": {
    "listingsail-local": {
      "command": "C:\\PATH\\TO\\ListingSailDesktop.exe",
      "args": ["--mcp"]
    }
  }
}
ONCE YOU’RE CONNECTED

Start with a look around.

Ask your assistant to check the license, then show a small set of free directory options. Review the requirements before you plan a campaign.

Use ListingSail license_status, then list_directories with fee="free" and limit=10. Summarize the saved requirements and unknowns. Make no changes or submissions.

CHOOSE WHERE YOUR WORK LIVES

Two routes. A clear choice.

☁

Hosted MCP

12 tools for licensed briefs, directory research, campaign planning, outcome records and public link checks. Works through the HTTPS endpoint.

Separate hosted workspace · Bearer license
▦

Local companion

14 tools with the desktop browser queue. Your local briefs, browser sessions and account handoffs stay on your Windows computer.

Local workspace · Desktop activation

Connecting grants access to tools, not permission to publish. Current website permissions still apply. CAPTCHA, sign-in, binding consent and payments need the appropriate human action. A prepared or received submission is not a published listing or a guaranteed backlink.

A FEW USEFUL DETAILS

Keep the connection clear.

Where do I put my license key?

For a remote connection, privately set LISTINGSAIL_LICENSE_KEY in the environment used by your AI client and restart it. Use your OS or client’s private environment settings. The configuration only references that variable. For the local companion, activate the key inside ListingSail Desktop. Never add the value to this page, a URL, a public file, or a chat.

Can I use a Claude web connector or an OAuth sign-in?

This endpoint uses a ListingSail license in a Bearer header. ListingSail does not currently provide an OAuth connection flow. Use a compatible client with header support, or connect Claude Desktop to the local Windows companion using the local guide.

The MCP URL shows “Method not allowed.” Is that an error?

Opening the endpoint as a normal web page sends a GET request. ListingSail returns HTTP 405 because this endpoint handles MCP JSON-RPC POST requests. Use your MCP client; the browser page is not a connection test. A 401 or inactive-license response in your client means you should check its private license setting and subscription.

Does hosted MCP control my desktop browser?

The hosted service and local companion use separate workspaces. Hosted MCP does not operate your computer’s browser or mailbox. For desktop browser campaigns, activate the Windows companion and connect its local stdio server. No workspace synchronization is implied.