← Registry

Learning Resources

profitforpartners.com

Provides reference and educational content on partnership terminology, partnership types, and the free Partner Playbook.

1 endpoint3 known toolsFirst detected September 22, 2026Last detected September 22, 2026

ENDPOINT 1

https://profitforpartners.com/api/mcp

No auth detected

MCP server metadata

Name
profitforpartners
Version
1.0.0
Capabilities
tools

Known tools 3

search_partnership_glossary

Search the partnership glossary: what a term means in partner-led growth, and which terms relate to it.

Inferred read-only
get_partnership_types

The six partnership types, each with what it is and what it costs in coordination.

Inferred read-only
get_playbook

What the free Partner Playbook covers, who it is for, and where to get it.

Inferred read-only

CONNECT 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.profitforpartners]
url = "https://profitforpartners.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "profitforpartners": {
      "type": "http",
      "url": "https://profitforpartners.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: profitforpartners
Remote MCP URL: https://profitforpartners.com/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": {
    "profitforpartners": {
      "url": "https://profitforpartners.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "profitforpartners": {
      "type": "http",
      "url": "https://profitforpartners.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "profitforpartners",
  "transport": "streamable-http",
  "url": "https://profitforpartners.com/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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.