Content Tools
salesleader.guide
Manage fictional staff writers and magazine pieces for a SalesLeader desk content system.
ENDPOINT 1
https://salesleader.guide/api/mcp
MCP server metadata
- Name
- salesleader-desk
- Version
- 1.0.0
Known tools 4
list_writersList the four fictional staff writers on the SalesLeader desk — slug, display name, pole, bio, and byline status.
Inferred read-onlyget_writerReturn one desk writer's full roster record — pole, bio, tier, byline status, canonical URL.
Inferred read-onlylist_magazine_piecesList juxtaposition pieces generated by the writers' desk — title, format, question, contributing writers.
Inferred read-onlyget_magazine_pieceReturn one full juxtaposition piece: the question, each writer's section body, and the Editor's weaving coda.
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.salesleader-desk]
url = "https://salesleader.guide/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"salesleader-desk": {
"type": "http",
"url": "https://salesleader.guide/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: salesleader-desk
Remote MCP URL: https://salesleader.guide/api/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": {
"salesleader-desk": {
"url": "https://salesleader.guide/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"salesleader-desk": {
"type": "http",
"url": "https://salesleader.guide/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "salesleader-desk",
"transport": "streamable-http",
"url": "https://salesleader.guide/api/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.