Agents Index

ShotPulled

Online

Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks.

Visit publisherConnectJSON

What it can do: 44 tools

  • register_grinderRegister a manual or electric grinder with its dial settings scheme. It becomes the active grinder only when no grinder is in use (none active, or the active one archived); otherwise call set_active with its grinder_id t
  • set_grinder_positionSet the current grinder collar position. source="measured" resets verification freshness. It replaces the stored position; no history of earlier positions is kept.
  • register_machineRegister an espresso or alternative preparation machine. It becomes the active machine only when no machine is in use (none active, or the active one archived); otherwise call set_active with its machine_id to switch to
  • set_equipment_archivedArchive or restore a grinder, machine, water, or scale.
  • update_grinderCorrect a registered grinder: its name, burrs, collar scheme, nominal step, layout, range or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field,
  • update_machineCorrect a registered machine (its name, control type, prep type and style, basket, boiler, accessories or notes), or record where its selectors stand (settings). Only the keys you send in fields change; send null to clea
  • update_scaleCorrect a registered scale: its type, resolution, capacity, capabilities, build or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a
  • update_waterCorrect a registered water: its name, type, mineral figures or notes. Only the keys you send in fields change; send null to clear an optional field (an empty string also clears a text field, but not a number or a closed
  • log_maintenanceLog a cleaning or maintenance job against a piece of equipment. A task that takes the thing apart opens a calibration epoch, and every recipe locked before it is read through that epoch's offset. Record the offset here i
  • set_maintenance_offsetRecord how far a maintenance job moved the reference, on an entry that opened a calibration epoch. Takes an ENTRY, not a piece of equipment: the offset belongs to the event that caused it, which is what lets several of t
  • set_maintenance_scheduleSet the user's own schedule for one maintenance task on one grinder or machine: their own interval, switching it off, or muting the reminder until a date. Only the keys you send in fields change; send every: null to go b
  • get_maintenance_guides read-onlyStep-by-step maintenance guides: tools, supplies, steps and warnings, in our own words with the maker's documents as sources. With no arguments, every guide for the user's current grinders and machines (and the water fil
  • list_maintenance_due read-onlyWhat maintenance is due across the user's current grinders and machines, most urgent first. Use it for "is anything due?". Only tasks with an interval compete: a task the machine counts and signals itself, one done by ha
  • register_waterRegister a custom or commercial water formulation.
  • list_waters read-onlyList registered waters for the account. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.
  • register_scaleRegister a brewing scale: the instrument that weighs the dose and the yield.
  • list_scales read-onlyList registered scales for the account. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.
  • register_programRegister a programmed shot button on a machine. A program cuts the shot off either by weight (program_type "volumetric", set target_volume_g) or by time (program_type "timed", set target_time_s). One machine can have a m
  • register_coffeeRegister a coffee that is NOT yet in list_beans, together with its first bag. It does not switch a coffee in use: it becomes active only when no coffee is in use (none active, or the active one archived or with every bag
  • set_activeSwitch the active bean, grinder or machine for this account. The numbers come from list_beans, list_grinders and list_machines. Registering a coffee, grinder or machine makes it active only when nothing of that kind is i
  • update_beanUpdate a coffee's own fields (roaster, origins, roast level, rest window, notes, rating…). Bag-shaped fields sent here (state, roast_date, bag_weight_g, grams_remaining, cost…) land on the coffee's CURRENT bag. Use updat
  • get_dial_state read-onlyRetrieve current dialing state, active context, recent shots, recommendations, and locked recipes.
  • log_shotLog an espresso or alternative shot/brew attempt. Uses the active context (bean/grinder/machine/program) unless overridden via bean_id/grinder_id/machine_id/program_id. ALWAYS pass bean_id explicitly when the user names
  • lock_recipeLock a successful shot as the reference dialing recipe for this equipment profile. It overwrites the recipe already locked for the same coffee, grinder, machine, program and drink intent, which keeps its recipe_id.
  • delete_shotDelete a logged shot from history. Restores the bean's remaining weight (which is derived from logged doses). Hard delete: there is no undo. To fix a mistake on an otherwise-valid shot, prefer update_shot over delete-and
  • update_shotCorrect fields on an already-logged shot in place, with no need to delete and re-log. Use for fixing a wrong dose/yield/time or grind label, re-filing a shot onto the right bean (bean_id), backfilling rating/tasting note
  • list_recipes read-onlyList recipes (all or filtered by equipment and status). The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back.
  • get_stats read-onlyGet compact flat usage stats for a grinder, machine, or bean.
  • list_grinders read-onlyList grinders registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back. Each row carries its ma
  • list_machines read-onlyList machines registered for the account, with status filter. The `id` on each row is the number this account knows that record by, counting from 1: safe to show, and what other tools expect back. Each row carries its ma
  • list_beans read-onlyList the coffees registered for the account, with status filter. Each coffee carries its bags[] (every purchase, with its own freshness and grams left) and current_bag_id; the row's top-level roast_date, state, grams_rem
  • grinder_math read-onlyDetermine steps/clicks difference and directions between setting labels (C3).
  • compute_age read-onlyCompute a bag's age in days off roast and its resting/staling verdict, for the coffee's current bag by default or for the bag named.
  • diagnose_shot read-onlyEvaluate shot metrics to provide ranked hypotheses (C6) and warn on flip-flops (G2) or fatigue (G6). Resolves the SHOT's own bean (age computed at the shot's pulled_at), never the active profile, and echoes it as bean_co
  • suggest_next_step read-onlyRetrieve the single next experiment step from the reasoning engine.
  • log_recommendationLog a recommended dialing change to allow contradiction/oscillation checking (G2).
  • get_rule read-onlyRetrieve the detailed text of a specific rule from the knowledge base by its rule ID.
  • get_kb_version read-onlyRetrieve the current version of the knowledge base.
  • kb_changelog read-onlyRetrieve the changelog showing updates and version differences for the knowledge base.
  • diagnose_preview read-onlySandbox-only diagnosis, writes nothing (no verdict, no recommendation-trail entry). Two modes: pass shot_id to dry-run a LOGGED shot (optionally overriding its sensory_tags, for the "what would this read as?" preview; th

…and 4 more.

Connect it

Claude Code
claude mcp add --transport http shotpulled https://mcp.shotpulled.com/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.shotpulled.com/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "shotpulled": {
      "url": "https://mcp.shotpulled.com/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "shotpulled": {
      "type": "http",
      "url": "https://mcp.shotpulled.com/mcp"
    }
  }
}

Questions

What does ShotPulled do?

Espresso dialing: log a shot, say how it tasted, get one change in your grinder's own clicks. It exposes 44 tools to AI assistants.

What tools does ShotPulled provide?

44 tools, including register_grinder, set_grinder_position, register_machine, set_equipment_archived, update_grinder, update_machine, update_scale, update_water, log_maintenance, set_maintenance_offset, set_maintenance_schedule, get_maintenance_guides….

How do I connect ShotPulled to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.shotpulled.com/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does ShotPulled require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is ShotPulled online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes ShotPulled?

shotpulled.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Cloud & DevOps