Marketing
saleshose.com
Manages SalesHose conversational lead-qualification forms, including creation, configuration retrieval, and embed code generation.
ENDPOINT 1
https://saleshose.com/mcp
MCP server metadata
- Name
- saleshose
- Version
- 1.0.0
SalesHose hosts conversational lead-qualification forms (score → route → book). Use create_lead_form to provision a live form and get embed snippets plus a one-time claim URL for the human owner. Public form data and submissions need no auth. Collected leads are only visible to the claimed owner in the dashboard.
Known tools 3
create_lead_formCreate a live SalesHose conversational lead-qualification form.
Potential side effectsget_formFetch a form's public config (title, theme, question blocks) by slug or form id.
Inferred read-onlyget_embed_codeGet copy-paste embed snippets (inline, popup button, chat bubble) and the hosted link for an existing form.
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.saleshose]
url = "https://saleshose.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"saleshose": {
"type": "http",
"url": "https://saleshose.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: saleshose
Remote MCP URL: https://saleshose.com/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": {
"saleshose": {
"url": "https://saleshose.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"saleshose": {
"type": "http",
"url": "https://saleshose.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "saleshose",
"transport": "streamable-http",
"url": "https://saleshose.com/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.