Marketing
shockchopper.com
Provides site identity, available operations, CRM vocabulary, and pipeline stage data for managing business leads and workflows.
ENDPOINT 1
https://shockchopper.com/mcp
MCP server metadata
- Name
- dfc-site-agent
- Version
- 1.2.0
Prospective customers: without signing in, call public_business_info, then public_find_local_office with the property's ZIP, then public_request_consultation once the person asks you to reach out. The office confirms the time. The other tools are for Shock Chopper staff and need sign-in. You are a Site Agent acting as the person who connected you. Call site_whoami first; its capabilities block is the truth about what you may read, propose and publish right now. Call site_operations next for per-kind payload schemas, required fields, allowed values, examples, permissions, side effects, recovery, and which operations this identity can execute. Call crm_context before any CRM proposal. CMS reads are direct: pages_list/pages_get, news_*, events_*, drafts_*, images_*, documents_*, brief_get, brief_board. Every change is filed with agent_proposal_create and written only when agent_proposal_publish is called by a person whose role allows that kind, or when an admin approves it in Management. Withdraw an open proposal with agent_proposal_reject. Pass parish_id only for a site in the current scope. Library uploads stay on REST POST /api/v1/site/images and /documents. On a site visit, read site_visit on lead_get. Ask how it went and for any prompt_for that is not none before complete_step. Then ask for photos. Upload them with POST /api/v1/site/images (file or files[], lead_id). Omit name.
Known tools 60
site_operationsFor this site and identity: which operations are available, required fields, allowed values, examples, permissions, side effects, recovery, and which you can execute.
Potential side effectspipeline_getStages with kind, position, transitions, working lead_counts (excludes archived).
Inferred read-onlylead_getLead, stage, open step, site_visit prompts (ask for missing info and photos), timeline, outreach preferences, booking, offers, and step history.
Inferred read-onlylead_timelineUnified contact history for a lead: intake, completed steps, quotes, texts.
Inferred read-onlylead_outreach_checkEmail suppression, SMS consent, and whether outbound is paused.
Potential side effectsagent_threads_listList this Site Agent's conversation threads for the bound parish.
Inferred read-onlyagent_proposal_publishApply an open proposal as the connecting person, if their role allows that kind (see site_whoami capabilities.*.publish).
Potential side effectssocial_channels_listThis location's Social Channels: the outbound presence it promotes itself, its news and its events on — social accounts, Google Business Profile, Nextdoor, review listings, website.
Inferred read-onlysales_channels_listCRM referral partners: associations, landscapers, builders, HOAs, chambers, parks.
Inferred read-onlysales_channel_getOne partner with its touch history and the leads it is credited with.
Inferred read-onlysales_channel_touchLog contact with a partner: called, emailed, visited, attended_event, referral_received, note.
Inferred read-onlysales_channel_events_listCurated dated events on this site's referral partners, soonest first.
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.dfc-site-agent]
url = "https://shockchopper.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dfc-site-agent": {
"type": "http",
"url": "https://shockchopper.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dfc-site-agent
Remote MCP URL: https://shockchopper.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": {
"dfc-site-agent": {
"url": "https://shockchopper.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dfc-site-agent": {
"type": "http",
"url": "https://shockchopper.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dfc-site-agent",
"transport": "streamable-http",
"url": "https://shockchopper.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.