eCommerce
blackdogranch.com
This MCP server provides access to BlackDogRanch's grass-fed beef products and related information.
ENDPOINT 1
https://matters.blackdogranch.com/mcp
MCP server metadata
- Name
- what-matters
- Version
- 1.0.0
What Matters is the user's personal list of action items. SECTIONS — every item lives in exactly one. action = the user owes the next move. waiting = owed TO the user; someone else moves next. note = worth knowing, no action. If the ball is in someone else's court it is waiting. No "today" section: anything due today or earlier surfaces at the top, so set "due" only for real deadlines. channel = where an item ORIGINATED (self/teams/email/meeting/other), not who typed it. priority defaults to medium; "high" only when someone is blocked or a deadline is close — mark everything high and the signal dies. note = prose context; links = up to 3 {label, url}, never raw URLs in the note. Never touch "settings". TWO WRITE PATHS. Scheduled or autonomous runs: get_document, then put_proposal — nothing lands until the user reviews it; set "agent" to your name ("Claude"), it headlines the review. Max 100 deltas; send the ones that matter. Live conversation, user asking directly: add_item / complete_item write straight through, with initiated "human" ("the user" = whoever is talking to you, any account). THE URGENT PUNCH-THROUGH: add_item with initiated "auto" AND priority "high" pushes a notification to the user's phone — the ONE sanctioned bypass of review. Only for someone-blocked-right-now; routine urgency kills the signal. Lower-priority auto adds land silently. ALWAYS stamp source_id on auto adds when a stable message or event id exists — the dedup key that stops the same thing being re-added under a reworded title. Never re-suggest anything deleted or in "rejections" — a dismissal is an answer. Active rules are enforced server-side; put_proposal reports drops. FOCUS — "focus" is up to 10 short terms the user says matter most. Weigh them in what you notice; it does NOT move an item's section or make it urgent. Set it only when the user asks, via manage_focus; never invent one. Condensed. Full guide — rules syntax, rejection→rule mining, fingerprints — is guide://what-matters; read it before any scheduled run.
Known tools 6
get_documentRead everything: action items, the record of what has already been dismissed, and "focus" — the handful of terms the user says matter most.
Inferred read-onlymanage_ruleCreate, change, pause or delete a standing rule, taking effect IMMEDIATELY with no review.
Potential side effectsmanage_focusReplace the list of things the user says matter most — people, projects, whatever they care about.
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.what-matters]
url = "https://matters.blackdogranch.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"what-matters": {
"type": "http",
"url": "https://matters.blackdogranch.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: what-matters
Remote MCP URL: https://matters.blackdogranch.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": {
"what-matters": {
"url": "https://matters.blackdogranch.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"what-matters": {
"type": "http",
"url": "https://matters.blackdogranch.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "what-matters",
"transport": "streamable-http",
"url": "https://matters.blackdogranch.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for blackdogranch.com was fetched 2026-08-15T01:34:36.342Z and is being refreshed.
blackdogranch.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.