← Registry

Productivity

useretainer.com

Provides tools for independent consultants to analyze stakeholders, set rates, track capacity, rank client profitability, and identify neglected relationships.

1 endpoint5 known toolsFirst detected October 5, 2026Last detected October 5, 2026

ENDPOINT 1

https://useretainer.com/mcp

No auth detected

MCP server metadata

Name
retainer
Version
1.1.0
Capabilities
tools.listChanged
Server instructions

Free tools from Retainer (useretainer.com), the CRM for independent consultants and fractional executives. map_stakeholders: map and prioritize the people on a client account. calculate_consulting_rate: what to charge, hourly, daily, or as a retainer. check_capacity: whether there is room for another client. rank_client_profitability: which clients pay best per hour. find_neglected_relationships: who has gone too long without contact. Fill in what you can from the conversation, then share the returned link so the user can adjust the numbers on the site.

Known tools 5

map_stakeholders

Sort stakeholders on a power/interest grid (Mendelow's matrix) into Manage Closely, Keep Satisfied, Keep Informed, and Monitor, with what to do for each group.

Inferred read-only
calculate_consulting_rate

Work out what an independent consultant should charge: minimum and recommended hourly rate, day rate, monthly equivalent, and a suggested monthly retainer or project day rate.

Potential side effects
check_capacity

Check whether an independent consultant has room for another client: available billable hours, current utilization, and whether they are under target, over target, or overcommitted.

Inferred read-only
rank_client_profitability

Rank a consultant's clients by revenue per hour, with totals and the average, and flag which clients earn below average.

Inferred read-only
find_neglected_relationships

Check which clients, past clients, or referral sources a consultant has gone too long without talking to.

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

.mcp.json

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

Settings → Connectors → Add custom connector

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

.vscode/mcp.json

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

Client-specific MCP configuration

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

Indexed

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