INDIVIDUAL MCP TOOL
write_follow_up_texts
Writes two dealership follow-up texts for a situation you describe: under 300 characters, names the rep and store, one question, a way out, no price or payment or trade value.
LIVE ENDPOINT
https://usepinpoint.ai/api/mcp
Connect to this endpoint to inspect the live schema for write_follow_up_texts and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description suggests a financial action.
Parent server
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.pinpoint-dealership-tools]
url = "https://usepinpoint.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pinpoint-dealership-tools": {
"type": "http",
"url": "https://usepinpoint.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pinpoint-dealership-tools
Remote MCP URL: https://usepinpoint.ai/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": {
"pinpoint-dealership-tools": {
"url": "https://usepinpoint.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pinpoint-dealership-tools": {
"type": "http",
"url": "https://usepinpoint.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pinpoint-dealership-tools",
"transport": "streamable-http",
"url": "https://usepinpoint.ai/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
check_appointment_ask— Deterministic check of one dealership appointment ask using six fixed text-pattern rules: day, clock time, holding the time, confirmation question, vehicle mention or readiness phrase, and follow-up.check_follow_up_text— Checks a dealership follow-up text message against eight practices: identifies the sender and store, refers to what the customer asked about, one question at most, a specific next step, no price or payment or trade value, an easy way out, two segments or fewer, no all-caps urgency.call_recording_consent— Whether one party or every party must consent before a phone call is recorded in a US state, the statute, a note for dealerships, and the greeting, outbound and text notices a dealership should use.ai_caller_disclosure— What a US state requires when an automated or AI voice assistant answers a dealership's missed calls or places an approved outbound call: the AI disclosure rule, the consent rule for automated calls, the statute, the federal baseline, and what the assistant should say.follow_up_cadence— The follow-up sequence for a dealership sales situation (new internet lead, missed inbound call, unconfirmed appointment, no-show, quote without an appointment, trade question without an appointment, text thread gone quiet, sold first week): the starting event and each step's timing, channel, purpose, message with the names filled in, and the reply that stops it.roleplay_card— A practice card for a dealership sales roleplay: a customer type (twelve, from the price shopper to the callback who went quiet) and an objection (eight, from "I need to think about it" to "just email me the numbers"): the customer's opening line, what they want and fear, their tells, the objection as the customer says it, the salesperson's goal, what a strong answer sounds like, and the feedback checklist.crm_note_checklist— What a complete CRM note carries after a dealership sales call or text thread, in five sections, with an example of a strong note and the lead statuses that mislead managers.call_scorecard— The eighteen-item pass-or-fail scorecard for a dealership sales call, in five groups (open, discovery, the ask, control, close and record), with the scoring rules and the four-minute review method.