Developer Tools
listingbooster.ai
Provides access to public discovery documents, summaries, pricing, and catalog for ListingBooster to support developer integration.
ENDPOINT 1
https://listingbooster.ai/mcp
MCP server metadata
- Name
- listingbooster-public-discovery
- Version
- 2026-06-26
This server exposes read-only public ListingBooster discovery tools. It does not expose customer data, billing, scheduling, social OAuth, or publishing actions.
Known tools 4
search_public_docsSearch ListingBooster public discovery documents and return matching public snippets.
Inferred read-onlyget_agent_edge_summaryReturn a concise public summary of Agent Edge and its approval-safe publishing posture.
Inferred read-onlyget_pricing_summaryReturn the public pricing summary and link to the authoritative pricing page.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.listingbooster-public-discovery]
url = "https://listingbooster.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"listingbooster-public-discovery": {
"type": "http",
"url": "https://listingbooster.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: listingbooster-public-discovery
Remote MCP URL: https://listingbooster.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"listingbooster-public-discovery": {
"url": "https://listingbooster.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"listingbooster-public-discovery": {
"type": "http",
"url": "https://listingbooster.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "listingbooster-public-discovery",
"transport": "streamable-http",
"url": "https://listingbooster.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.