MCP server

ShotPulled Official

com.shotpulled/shotpulled

Checked 25 Oct 2026, 20:29 UTC · Connected to it and listed its tools

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

Website

At a glance

Type

MCP server

Publisher

shotpulled.com (verified by the MCP Registry)

Status

Working at last check

Tools

44

Token cost

About 17,338 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

25 Oct 2026, 20:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http shotpulled https://mcp.shotpulled.com/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.shotpulled]
url = "https://mcp.shotpulled.com/mcp"

Gemini CLI

{"mcpServers":{"shotpulled":{"httpUrl":"https://mcp.shotpulled.com/mcp"}}}

Cursor

{"mcpServers":{"shotpulled":{"url":"https://mcp.shotpulled.com/mcp"}}}

VS Code

{"servers":{"shotpulled":{"type":"http","url":"https://mcp.shotpulled.com/mcp"}}}

Antigravity

agy mcp add shotpulled https://mcp.shotpulled.com/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"shotpulled","server_url":"https://mcp.shotpulled.com/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"shotpulled","server_url":"https://mcp.shotpulled.com/mcp"}

Tools

• compute_age ~113 tokens
  Compute 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.
• delete_shot Deletes data · ~117 tokens
  Delete 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-relog.
• diagnose_preview ~451 tokens
  Sandbox-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; the shot's own bean and its age at pulled_at are used), or pass the full metric se
• diagnose_shot ~208 tokens
  Evaluate 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_context, so diagnosing an older or differently-filed shot is always safe. The engi
• get_dial_state ~54 tokens
  Retrieve current dialing state, active context, recent shots, recommendations, and locked recipes.
• get_kb_version ~41 tokens
  Retrieve the current version of the knowledge base.
• get_maintenance_guides ~191 tokens
  Step-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 filter fitted in each). With guide_ids, those guides; the ids come from maintenance
• get_rule ~80 tokens
  Retrieve the detailed text of a specific rule from the knowledge base by its rule ID.
• get_stats ~92 tokens
  Get compact flat usage stats for a grinder, machine, or bean.
• grinder_math ~88 tokens
  Determine steps/clicks difference and directions between setting labels (C3).
• kb_changelog ~50 tokens
  Retrieve the changelog showing updates and version differences for the knowledge base.
• list_beans ~189 tokens
  List 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_remaining and age fields are the current bag's. The `id` on each row is the number
• list_grinders ~265 tokens
  List 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 maintenance block: every task with its class (S schedule, H habit, Y symptom, A th
• list_machines ~277 tokens
  List 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 maintenance block, researched per model: every task with its class, due state, wha
• list_maintenance_due ~209 tokens
  What 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 habit or when a symptom shows, and one the maker advises against never appear. Eac
• list_recipes ~148 tokens
  List 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.
• list_scales ~120 tokens
  List 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.
• list_shots ~399 tokens
  List shot history with support for pagination and filtering. Every shot carries a derived taste_pending flag (1 = logged with no sensory tags, no rating, and no tasted flip: the tasting is still owed and can be backfilled with update_shot).
• list_waters ~120 tokens
  List 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.
• lock_recipe ~126 tokens
  Lock 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.
• log_maintenance ~920 tokens
  Log 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 if you counted the clicks while reassembling, which is the one moment anybody act
• log_recommendation ~166 tokens
  Log a recommended dialing change to allow contradiction/oscillation checking (G2).
• log_shot ~1263 tokens
  Log 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 a specific coffee, so the shot cannot land on the wrong bag. Backdate with pulle
• merge_beans ~274 tokens
  Fold one coffee into another when the same coffee was registered twice. Every bag, shot, recipe and recommendation of from_bean_id moves to into_bean_id; the active coffee follows if it was the one merged away; origins move only if the target has none. Where both hold a locked recipe for the same gr
• register_bag ~525 tokens
  Register another bag of a coffee that is already in list_beans: the same roaster's product, bought again. It keeps the coffee's recipes, notes and history; only the purchase facts (roast date, weight, price, state) are new. Does not change the active coffee. Returns a bag_id: bag numbers are their o
• register_coffee ~1369 tokens
  Register 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 finished); otherwise call set_active with its bean_id when the user starts brew
• register_grinder ~562 tokens
  Register 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 to switch to it. The `active` field of the reply says which.
• register_machine ~609 tokens
  Register 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 it. The `active` field of the reply says which.
• register_program ~347 tokens
  Register 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 mix of both. A program_number the machine already has is overwritten with these s
• register_scale ~645 tokens
  Register a brewing scale: the instrument that weighs the dose and the yield.
• register_water ~251 tokens
  Register a custom or commercial water formulation.
• set_active ~304 tokens
  Switch 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 in use (the `active` field of the reply says which), so call this to start using
• set_equipment_archived ~134 tokens
  Archive or restore a grinder, machine, water, or scale.
• set_grinder_position ~171 tokens
  Set the current grinder collar position. source="measured" resets verification freshness. It replaces the stored position; no history of earlier positions is kept.
• set_maintenance_offset ~322 tokens
  Record 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 them compose for a recipe locked before all of them. Zero is a legitimate measure
• set_maintenance_schedule ~786 tokens
  Set 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 back to the maker's guidance and muted_until: null to unmute. Use it when the use
• suggest_next_step ~61 tokens
  Retrieve the single next experiment step from the reasoning engine.
• update_bag ~674 tokens
  Change bag-level facts on one bag of a coffee: open, seal, freeze, thaw or finish it, correct its roast date, weight, grams left or price. Bag numbers come from the bags[] on list_beans (or current_bag_id). For the coffee itself (roaster, origin, roast level, rest window, notes), use update_bean.
• update_bean ~1434 tokens
  Update 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 update_bag when it has more than one. Changing dial_category changes what the engine
• update_grinder ~889 tokens
  Correct 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, but not a number or a closed list). Required fields can be changed but not clea
• update_machine ~705 tokens
  Correct 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 clear an optional field (an empty string also clears a text field, but not a number
• update_scale ~494 tokens
  Correct 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 number or a closed list). Required fields can be changed but not cleared. field
• update_shot ~797 tokens
  Correct 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 notes, or fixing the timestamp (pulled_at). Changing grind_label re-derives the nume
• update_water ~298 tokens
  Correct 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 list). Required fields can be changed but not cleared. fields may be omitted whe

Browse

• Notes and wikis
• Running code
• Maps and places
• Food and recipes

Related MCP servers

• Brewmark
  Grind-setting conversion between 77 coffee grinders, plus dial-in charts for every model.
• Espresso Steals
  Espresso gear price history: live Amazon prices, 2+ years of daily data, BUY calls at verified lows.
• Percolate
  Search the Percolate specialty coffee database: 1,100+ coffees with brew recipes and pairings.
• ZeroWidth Napkin
  Draw boards, write docs and sheets, and build decks with your brand in Napkin.
• BagIQ MCP
  Analyse disc golf bag gaps and overlap, recommend discs, and open an interactive Bag Map.
• stake.link Agents (stakedotlink.money)
  Community-built stake.link tools: live stLINK, SDL and reSDL data, unsigned transaction builders.
• bordeaux.guru — Bordeaux en primeur & terroir
  First-hand Bordeaux en primeur tasting notes, appellation climate, phenology and terroir.
• Country Calling Codes
  Calling codes, phone analysis, dialing guidance, batch normalization and calling windows.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/com.shotpulled/shotpulled.svg)](https://aptlynx.net/servers/com.shotpulled/shotpulled)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents