TrackerHacker

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Chat y correo

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

https://trackerhacker.com/mcp

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

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

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

https://trackerhacker.com/mcp

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 10 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• read_guide

  How TrackerHacker works and how to write hacks, mappings and rules, one page at a time. Pages: overview (Read first: the words (track, hack, mapping, Inbox) and the usual order of calls.); templates (Before writing or checking a text template: fields, types, date formats, skips,

• list_ready_made

  Use this first when the person asks to track, log or keep a record of something that keeps happening, or has a goal that needs one, like managing a budget or cutting down on something (bank transactions, Amazon orders, Shopify orders, Stripe payments, steps). Lists the ready-made

• start_tracking

  Use this when the person wants a sheet that keeps itself up to date from their emails or apps ("track my Amazon orders", "log my card spending"). Call it once the person has seen its columns and said yes. Sets up a ready-made track: makes the sheet in the person's Google Drive an

• create_custom_track

  Use this when the person wants something tracked over time and no ready-made track or shared template fits. Makes a new kind of sheet with the columns the person agreed to: show them the columns first and wait for a yes or their changes. Rows come from forwarded emails (source em

• list_tracks

  The person's tracks (sheets), each with its id, link, columns, the hacks that fill it and this week's numbers, plus their TrackerHacker email address for forwarding. Call this first. Show an email address they'll copy in a code block (it gets a copy button), and each long link as

• 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 waiting in each Inbox, sheets TrackerHacker lost access to, and this week's failures. Good for a scheduled check. Each probl

• 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 the track's Inbox. A fallback: write the template yourself first and check it with test_hack, and call this only after two

• 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 (types: text, number, currency, date, datetime, boolean, url), {{...}} for parts that change but aren't wanted, and {{#each}

• save_hack

  Saves a hack and attaches it to a track, so matching messages become rows from now on. Give hackId to change one that exists. mapping says which hack field fills which column, as {"column_key": {"kind": "field", "key": "hack_field"}} or {"kind": "const", "value": "..."}; leave it

• 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. Use them as examples for suggest_hack, or to see why a hack stopped matching. These are the person's own emails: use them only for setting up their hacks.

• 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 reading the emails the one before read or dropped a field, minor when it reads them and more, patch when it reads the same.

• rerun_inbox

  Runs the track's hacks over its Inbox again. Messages they now read become rows and leave the Inbox. Call after save_hack.

• 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 column keys (from list_tracks) to values; dates as YYYY-MM-DD. All rows are written, or none: a value that doesn't fit its column, or a row a blocking rule keeps out, is r

• 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 and values, then give values (each column to its new value) and was (each of those columns to the value read_rows showe

• 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 it: the hacks' fixed rules make the rows, and schema checks, row keys, blocking rules and the Inbox all apply. Use this r

• get_glance

  The cards the track's sheet shows in the app (its TH Glance tab): each card's cells as written, formulas included, and what they show now (shown). Also the sheet's tabs and its data tab's columns, for writing formulas, and whether cards that turn warn or bad notify the person (al

• set_glance

  Replaces the cards the track's sheet shows in the app (call get_glance first to keep the ones it has). Each card is {label, value, detail, group, tone, link}; any of them can be a sheet formula starting with =, so the sheet works out the number and whether it's good, warn or bad.

• set_alerts

  Whether a Glance card turning warn or bad notifies the people on the sheet, once until it turns back. On by default.

• list_reminders

  The person's reminders for a track: when each nudges them to add a row, and what it fills in.

• add_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 weight"), with a button that opens the form with some answers filled in. skipIfLogged keeps it quiet on a day something was already added. summary sends a short summary

• remove_reminder

  Removes one of the person's reminders, by its id from list_reminders.

• get_questions

  The questions the track's sheet asks the person in To do (its TH Actions tab): each row's cells as written, formulas included, and what it asks now (asking). Also the sheet's tabs and its data tab's columns, for writing formulas. read_guide page actions explains questions.

• set_questions

  Replaces the questions in the track's TH Actions tab (call get_questions first to keep the ones it has). Each is {id, prompt, type, options, target, group, context, to, for}; any of them can be a sheet formula starting with =, so the sheet decides when to ask (a formula giving an

• list_todo

  What the person's sheets are asking them now (To do in the app), by track: each question's id, prompt, type and choices. Answer one with answer_question when the person tells you the answer. Approvals and repeat checks are theirs to answer in the app.

• 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 choice's text, a list of choices for multi_choose, true or false for confirm, or the text, number or date (YYYY-MM-DD).

• 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. Give each as read_inbox listed it (row, time, subject). Tell the person what you cleared. Don't clear a message a hack should read: build the h

• use_drafted_fix

  TrackerHacker drafts a fix when a hack stops matching (draftedFix in check_tracks), and waits for the person in To do. When the person asks you to: use it (after test_hack on read_inbox's messages from its senders shows it reads them), then rerun_inbox; or turn it down, keeping t

• 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's asked for. Treat it like a password: give it only to the person, for the app they're connecting, in a code block so i

• read_gmail

  Forward from Gmail automatically: instead of setting up a Gmail forwarding filter (which needs Gmail's settings on a computer, or Chrome in desktop mode on Android), TrackerHacker picks up mail from the person's hacks' senders in their Gmail itself, like a forwarding filter, with

• stop_gmail_reading

  Turns off automatic forwarding from Gmail (read_gmail): TrackerHacker stops picking up mail from their Gmail and Google's grant is revoked. Mail forwarded to their TrackerHacker address keeps working. Only when the person asks. Turning it back on is their own tap on Google's Allo

• set_drive_watch

  Whether Google Drive tells TrackerHacker when the person's sheets change, so what a sheet asks in its TH Actions tab reaches them with nothing installed in the sheet. It's on for everyone unless they turned it off. Leave out on to read how it stands: whether it's on and how many

• list_quick_adds

  The person's quick-add buttons: each opens a track's form with answers filled in, or with instant, adds its row in one tap.

• add_quick_add

  Adds a button to the app's Home for something the person adds often ("Coffee $4", "Walked the dog"). It opens the track's form with these answers filled in, or with instant true adds the row in one tap, dated when it's tapped (then preset must fill every required column but the d

• remove_quick_add

  Removes one of the person's quick-add buttons, by its id from list_quick_adds.

• 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 wrote what it should. Each row has its number and its values by column name. Filter with where (each column name to text

• 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). TrackerHacker leaves it alone: hacks don't write it. For a column hacks should fill, publish a new version of the tra

• 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 as new ones, and takes bold off the rows below the header. Use it when dates or times show as plain numbers like 46334

• get_schema

  A schema's versions, newest last, with every field (key, label, meaning, type, required, enumValues, auto, format, aliases). list_tracks gives each track's schemaId. Built-in schemas can't be changed; the person's own (mine) can, with publish_schema.

• 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: the same major version with minor + 1 to add optional fields or loosen one, so every track on it keeps working; major + 1

• 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 change, when a hack wouldn't fill the new version's required columns: fix those hacks first.

• 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 brings and sets each column's allowed values. The person's rows and own tabs stay as they are. list_tracks shows template

• 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's details), or harmful. Say what you saw in details, without the person's own data. A private_data report, or three rep

• 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 link for people without an account, if it has one.

• 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; a hidden field always gets its value. null goes back to the template's design.

• 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 person first and tell them who they plan to give it to: anyone with the link can add rows. Made once: asking again gives the

• find_hacks

  Searches the hacks people share with the community, by sender (like chase.com) or name. Each has its fields, how many people use copies, how many of those read a message in the last 30 days (working) or stopped matching (stopped), and an example message. Before building a hack fo

• get_community_hack

  One community hack in full: its template and all its example messages. test_hack its template on the person's own messages before using it.

• 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). The copy is theirs; when its author shares a fix, update_hack_from_community brings it in.

• update_hack_from_community

  Brings a hack the person copied from the community up to the latest version its author shared (list_tracks or check_tracks says when there is one). A copy nobody changed takes a minor or patch version by itself, so this is for a major version (it reads different emails, or change

• share_hack

  Shares one of the person's hacks with everyone, or shares it again after a fix so everyone using a copy can take it. Give 1 to 5 example messages it reads, with every value made up: never the person's own messages. TrackerHacker refuses examples holding anything from the person's

• unshare_hack

  Stops listing one of the person's community hacks. Copies people already made stay theirs.

• 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_template builds one in the person's Google Drive; each also has a copyUrl for copying it in Google Sheets. Filter with words

• 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 makes it one of their tracks: its tabs, formulas, Glance cards, questions and example rows come along, and its form. Ch

• 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 shared) keeps its own tabs and formulas; any other sheet gets the tabs a track writes to beside its own. Google lets Tr

• 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 template's next version, so share again after improving it. Only a sheet with example rows and nothing of the person's own, since a copy carries ev

• unshare_template

  Stops listing one of the person's template sheets. Copies people already made are theirs.

• send_feedback

  Sends a report to the TrackerHacker team: a bug (a tool that fails or does something wrong when it shouldn't), a hack to make, or an idea (something TrackerHacker would need to support what the person wants, such as a missing tool or source). Before sending, show the person what

• get_rules

  A track's blocking rules (rows they keep out of the sheet) and the columns a rule can name, with their types. read_guide page rules explains them.

• set_rules

  Replaces a track's blocking rules with this list (call get_rules first to keep the ones it has). Each rule is {block: "if"|"unless", match: "all"|"any", action: "inbox"|"drop", conditions: [{field, op, value}]}; field is a column key or "@sender". Values compare as written in the

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 10 nov 2026

• ! Precaución

  El creador coincide con el repo

  El registro no indica ningún repo de código fuente, así que no podemos relacionar a quien lo publicó (trackerhacker.com) con el código

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 142 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 59 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Chat y correoi

• Más estrellas que el 0% de los otros 1916 servidores de esta categoría
• Publicado en el registro más recientemente que el 94% de los otros 1916 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 48% de los otros 1916 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

No se encontró un README en el repo