Force-free dog training: step-by-step plans, the Handbook and product facts. Read-only.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Facts about Push Drop Stick itself: what the app is, who wrote its training content, the force-free method, platforms (iPhone, Apple Watch, web, Android status), what is free, subscription prices, what Coach (the AI trainer) is and where it stops, how training data is handled, and links. Use for questions about the product, e.g. "Is Push Drop Stick free?", "Is it on Android?", "What is Coach?". Quote this rather than guessing.
This tool takes no arguments.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http plans https://pushdropstick.com/mcp/public
Facts about Push Drop Stick itself: what the app is, who wrote its training content, the force-free method, platforms (iPhone, Apple Watch, web, Android status), what is free, subscription prices, what Coach (the AI trainer) is and where it stops, how training data is handled, and links. Use for questions about the product, e.g. "Is Push Drop Stick free?", "Is it on Android?", "What is Coach?". Quote this rather than guessing.
No arguments.
{
"type": "object",
"properties": {}
}The full text of one document from `search`, as markdown: a training plan (id "plan:<ref>") with every step, a Handbook entry or section ("handbook:<id>"), or the product facts ("about"). Returns {id, title, text, url, metadata}; cite `url`.
| Argument | Type | Description |
|---|---|---|
| id* | string | An id from search. |
{
"type": "object",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"description": "An id from search."
}
}
}The full content of one public plan: description, equipment, cues, and every step with setup, instructions, success/failure criteria, set size and the rule for moving on, plus the push/drop/stick execution rules. Pass the `plan` ref from search_plans or list_plans. Link the user to the returned `url`; plan text may be quoted with attribution to its `author`.
| Argument | Type | Description |
|---|---|---|
| plan* | string | The `plan` ref from search_plans or list_plans: a slug (library plan) or "handle/slug". |
{
"type": "object",
"required": [
"plan"
],
"properties": {
"plan": {
"type": "string",
"description": "The `plan` ref from search_plans or list_plans: a slug (library plan) or \"handle/slug\"."
}
}
}How to read and execute a Push Drop Stick plan: the force-free marker-training philosophy and the push/drop/stick set mechanics that every plan shares.
No arguments.
{
"type": "object",
"properties": {}
}Browse the public plan library by group (e.g. Basic Manners, Grooming & Handling, Positions, Tricks). Use when the user wants to see what can be trained or what a category holds, rather than an answer to one problem. Without `group`: every group with its plans' names, refs and urls. With `group`: that group's plans with summaries and step counts.
| Argument | Type | Description |
|---|---|---|
| group | string | Optional group name, as list_plans (no arguments) returns it. |
{
"type": "object",
"properties": {
"group": {
"type": "string",
"description": "Optional group name, as list_plans (no arguments) returns it."
}
}
}Read the Handbook. `id` = an entry id from search_handbook (e.g. "threshold", "geartoavoid", "faqtreats") → the whole entry as markdown, with its canonical url and the entries it links to. `id` = a section slug (e.g. "fear-emotion", "gear", "faq") → the section's introduction and its entries. No `id` → the table of contents: every section and entry with urls.
| Argument | Type | Description |
|---|---|---|
| id | string | An entry id or title, or a section slug. Omit for the table of contents. |
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "An entry id or title, or a section slug. Omit for the table of contents."
}
}
}One search across the whole site: training plans, Handbook articles, and (for questions about the product) the facts page. Returns `results` [{id, title, url, text}]; pass an `id` to fetch for the full document. When you already know you want plans or Handbook articles, search_plans or search_handbook give richer results.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (1-25). |
| query* | string | What to look for, in plain words. |
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 10,
"maximum": 25,
"minimum": 1,
"description": "Max results (1-25)."
},
"query": {
"type": "string",
"description": "What to look for, in plain words."
}
}
}Search the Push Drop Stick Handbook: 140+ short articles by a certified force-free trainer (Allison Wells, CTC). Covers how dogs learn (positive reinforcement, punishment, extinction, classical conditioning), fear and reactivity (threshold, trigger stacking, desensitization and counter-conditioning, dogs who wore shock or prong collars), teaching techniques (markers, lures, shaping, duration/distance/distraction), gear (harnesses, head halters, muzzles, why not prong or shock collars), a FAQ (treats, where and how often to train), and how the app and Coach work. Use for "what is", "why" and "should I" questions. Returns entry ids, the most relevant paragraph and canonical urls; read_handbook returns a whole entry.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (1-25). |
| query* | string | A question or topic, in plain words. |
| section | string | Optional: search only this section. |
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 6,
"maximum": 25,
"minimum": 1,
"description": "Max results (1-25)."
},
"query": {
"type": "string",
"description": "A question or topic, in plain words."
},
"section": {
"enum": [
"purpose",
"faq",
"learning-science",
"fear-emotion",
"how-the-app-works",
"using-the-player",
"teaching-techniques",
"gear",
"coach",
"your-devices",
"training-with-coach",
"writing-plans"
],
"type": "string",
"description": "Optional: search only this section."
}
}
}Find step-by-step, force-free training plans for a behavior, problem or command, e.g. "pulling on leash", "crate training", "come when called", "nail trims", "jumping on guests". BM25 ranked. Returns each plan's `plan` ref, summary, step count, author and canonical `url` to recommend. Next: get_plan for the full steps. For concepts or advice ("what is threshold", "are prong collars ok") use search_handbook instead.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Max results (1-25). |
| query* | string | What to train, or the problem to solve, in plain words. |
| species | string | Optional filter: only plans written for this species, lowercase singular ("dog", "cat", ...). Most plans are "dog". |
| language | string | Optional filter: only plans written in this language (ISO 639-1 code, e.g. "en", "it"). Most plans are "en". |
{
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 8,
"maximum": 25,
"minimum": 1,
"description": "Max results (1-25)."
},
"query": {
"type": "string",
"description": "What to train, or the problem to solve, in plain words."
},
"species": {
"type": "string",
"description": "Optional filter: only plans written for this species, lowercase singular (\"dog\", \"cat\", ...). Most plans are \"dog\"."
},
"language": {
"type": "string",
"description": "Optional filter: only plans written in this language (ISO 639-1 code, e.g. \"en\", \"it\"). Most plans are \"en\"."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 13, 2026.