# Trackerhacker MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.trackerhacker%2Fmcp
Registry id: `mcp-registry/com.trackerhacker/mcp`
Status: live (checked 2026-11-22T16:03:00.017Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 999
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "trackerhacker-mcp-server": {
      "type": "http",
      "url": "https://trackerhacker.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http trackerhacker-mcp-server https://trackerhacker.com/mcp
```

## Tools (68)

- `add_column`: Adds a column of the sheet's own after its last one, for the sheet's formulas or the answers to its questions to fill (a Category the sheet asks about, a Status
- `add_rows`: Adds rows the person tells you about to a track, like a purchase they made in cash. Each row is an object of columns to values, by column key (from list_tracks)
- `add_to_list`: Adds one line to another tab of the track's sheet, a list it keeps beside its rows (plans, money moved between budgets, chores, people on a rota), when the pers
- `also_fill`: One service, several sheets: a track's webhook link, or one of its scheduled fetches, can also fill other tracks of the person's, each reading it with its own h
- `answer_question`: Writes the person's answer to one of their sheet's questions (from list_todo), as if they tapped it in To do. Only answer what the person told you. value is the
- `change_list_line`: Reads, changes or removes lines of a list (another tab of the track's sheet, see add_to_list). With trackId and tab alone it gives the list's newest lines, each
- `change_template`: Moves a track to another layout for its schema (a ready-made template like a monthly budget, by its id), or to its template's newest version: adds the tabs it b
- `check_data`: Reads one track's data tab and names rows its formulas would read wrong: the same key on two rows (an update finds only the first), a column every row needs lef
- `check_tracks`: What needs attention across all the person's tracks: hacks that stopped matching their senders' messages (the sender probably changed its emails), messages wait
- `connect_sheet`: Makes a Google Sheet the person already has into one of their tracks, from its link, so hacks can write to it: a copy of a template sheet (like a budget someone
- `create_custom_track`: Use this when the person wants something tracked over time and no shared template fits. Makes a new kind of sheet with the columns the person agreed to: show th
- `dismiss_inbox`: Removes messages from the track's Inbox that will never be rows, like newsletters or one-off mails, so check_tracks stops counting them. This can't be undone, s
- `email_senders`: The senders whose emails the person tracks, each for one or more topics (a track's schemaId; every track on a topic gets them). This is the usual way to track e
- `find_hacks`: Searches the hacks people share with the community, by sender (like chase.com) or name. With trackId, what fills that track instead: TrackerHacker's ready-made 
- `find_row_email`: For one row of a track (its number from read_rows), a Gmail search for the email it was made from: from the senders of the hack that wrote it, around the day Tr
- `find_templates`: Template sheets people share: whole sheets built for something (a budget, a shop's orders), with their tabs, formulas, Glance cards and questions. install_templ
- `format_sheet`: Gives each column of a track's sheet the date or number format its schema promises (dates as dates, money with two decimals), for the rows already there as well
- `get_form`: The track's form for adding a row by hand: its fields, its design (title, intro, thanks, askName, and each field's question, help, or hidden value), and its lin
- `get_glance`: What the track's Glance cards show now (cards: label, value, detail, tone), and whether cards that turn warn or bad notify the person (alerts). This answers "am
- `get_questions`: The questions the track's sheet asks the person in To do (its To do tab): each row's cells as written, formulas included, and what it asks now (asking). Also th
- `get_rules`: A track's blocking rules (rows they keep out of the sheet) and the columns a rule can name, with their types.
- `get_schema`: A schema (the app shows it to the person as a topic) and its versions, newest last; retired when its owner took it out of search, with the successor to use inst
- `get_sheet_guide`: How the track's sheet is meant to be used, in its author's words: the lines of its Start here tab (startHere), the lines its author headed For assistants (forAs
- `get_webhook_link`: The private link other apps (Zapier, IFTTT, iOS Shortcuts, a script, a shop) post JSON or text to, to add rows through the track's hacks. Made the first time it
- `gmail_forwarding`: Whether Forward from Gmail automatically is offered and on, and the link the person opens to turn it on with one Allow tap, on any device. Instead of a Gmail fi
- `hack_versions`: Every version kept of a hack, newest first, with its template, senders and subject words. TrackerHacker numbers them itself: major when the template stopped rea
- `install_template`: Builds a new sheet in the person's Google Drive from a template sheet people share (from find_templates), once the person has seen its columns and said yes, and
- `list_todo`: What the person's tracks are asking them now (To do in the app), by track: each question's id, prompt, type and choices, and whether the track's To do alerts ar
- `list_tracks`: The person's tracks (sheets), each with its id, link, columns, the hacks that fill it (each with its state: On, Off, Stopped matching, or Paused when it's over 
- `publish_schema`: Publishes the next version of one of the person's own schemas (from get_schema, where mine is true), kept private. Give the whole schema with its new version: t
- `quick_adds`: Quick adds: buttons on the app's Home, for something the person adds often ("Coffee $4", "Walked the dog"): each opens a track's form with answers filled in, or
- `rate_template`: Gives a public template the person copied and connected 1 to 5 stars, with an optional short review (up to 280 characters, no links, email addresses or long num
- `read_guide`: How TrackerHacker works and how to write hacks, mappings, rules, cards and questions, one page at a time. Pages: overview (Read first: the words (track, hack, m
- `read_inbox`: Messages that reached a track but didn't make a row (no hack read them, or a rule blocked them), newest first, with why: up to 20 of the newest 50. Give from to
- `read_rows`: Reads the rows in a track's sheet, newest last, to answer the person's questions about them ("what did I spend on dining this month?") or to check that a hack w
- `reminders`: A reminder nudges the person on their phone or browser at a time of day, on some days of the week, to add a row ("Log your mileage"), with a button that opens t
- `report_community_hack`: Reports a community hack someone else shares: broken (it reads messages wrong or writes wrong values), private_data (its template or examples hold a real person
- `rerun_inbox`: Runs the track's hacks over its Inbox again, 50 messages at a time from the newest. Messages they now read become rows and leave the Inbox. save_hack, use_commu
- `save_hack`: Saves a hack and attaches it to a track, so matching messages become rows from now on, then runs the track's Inbox again so messages already waiting become rows
- `scheduled_fetches`: For a service that has the data but never sends it (a social network's post stats, a shop's stock, an API with no webhooks): every 1, 3, 6, 12 or 24 hours Track
- `send_feedback`: Sends a report to the TrackerHacker team: a bug (a tool that fails or does something wrong), a hack to make, an idea (what TrackerHacker would need to support w
- `send_message`: Hands an email (its From address, subject and text) or a JSON body to one of the person's own tracks, to be read by its hacks exactly as if they had forwarded i
- `set_alerts`: Glance alerts: whether a Glance card turning warn or bad notifies the people on the track, once until it turns back. On by default. (To do alerts, whether a new
- `set_card_value`: Changes the cell a Glance card names in its set column (get_glance shows it as set, like 'Goals'!B2), when the person tells you the new value: a goal, an amount
- `set_drive_watch`: Whether Google Drive tells TrackerHacker when the person's sheets change, so what a sheet asks in its To do tab reaches them with nothing installed in the sheet
- `set_form`: Sets how the track's form asks for a row: {title, intro, thanks, askName, fields: [{key, label, help, hidden, value}]}, fields by column key in the order asked;
- `set_glance`: Replaces the cards the track's sheet shows in the app with this list (call get_glance with forEditing: true first, and send the ones it has along with yours). A
- `set_questions`: Replaces the questions in the track's To do tab with this list (call get_questions first, and send the ones it has along with yours). A list shorter than the on
- `set_rules`: Replaces a track's blocking rules with this list (call get_rules first, and send the ones it has along with yours). A list shorter than the one it has is refuse
- `share_form`: Makes the link that lets anyone who has it add a row to the track through its form (volunteers logging hours, guests signing up), with a bot check. Ask the pers
- `share_hack`: Shares one of the person's hacks with everyone. Community hacks belong to the community, one for each kind of email a sender sends: the hack's wording goes into
- `share_schema`: Shares one of the person's own schemas (mine in get_schema) with everyone (public, listed in the community, so other people's sheets and hacks can use it) or wi
- `share_template`: Shares one of the person's sheets as a template others copy: its tabs, formulas, Glance cards and form go with it; each share is the next version. Only a sheet 
- `start_from_hack`: Starts tracking from a hack instead of a template, in one step: a service like Shopify or Instagram (a ready id from find_templates' hacks or find_hacks) or a c
- `start_tracking`: Older way to start, kept for assistants that still use it: prefer find_templates and install_template, then find_hacks with the new trackId. Starts from the tem
- `stop_gmail_forwarding`: Turns off Forward from Gmail automatically and revokes Google's grant. Mail forwarded to their TrackerHacker address keeps working. Only when the person asks; t
- `suggest_hack`: Suggests a hack (a template that reads one kind of message) from an example email or JSON body, for a track. It's checked against similar messages waiting in th
- `template_reviews`: Lists the reviews of templates the person shares, newest first (hidden: reports hid its words from the page). With reviewId and reply, answers one as the templa
- `test_hack`: Shows what a hack template reads from example messages, without saving anything. Templates are the message's fixed text with {{field:type}} where values go (typ
- `turn_on_ready_hack`: Turns on one of TrackerHacker's ready-made sources for a track (from find_hacks with its trackId, under ready): a service that posts to the sheet's link (Shopif
- `unshare_template`: Stops listing one of the person's template sheets. Copies people already made are theirs.
- `update_from_template`: For a sheet copied from a shared template sheet (copiedFrom in list_tracks): which version of the template it's on, the newest, and what updating adds, tab by t
- `update_hack_from_community`: Brings a hack the person copied from the community up to the community hack's latest version (list_tracks or check_tracks says when there is one). A copy nobody
- `update_row`: Changes cells of one row in the person's own track, when they correct something ("that burrito was 750 calories, not 600"): read_rows first for the row's number
- `upgrade_track`: Moves a track to the next major version of its schema: renames the sheet's headers the version renames and moves its hacks' mappings. Refused, with what to chan
- `use_community_hack`: Copies a community hack into the person's account and attaches it to a track, mapping its fields to columns by name unless you give a mapping (as in save_hack),
- `use_drafted_fix`: When a hack stops matching, TrackerHacker works out an update for it (draftedFix in check_tracks) that waits for the person in To do, where the buttons are Upda
- `use_starter`: Builds a track's sheet on the TrackerHacker starter, the base for a template instead of a blank sheet, or updates it to the newest starter. Adds only the tabs i

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
