Skip to content

BlogClinicalTracker.org + Lindy

ClinicalTracker.org + Lindy: a weekly agent that asks for changes on the trials you watch and sends a plain summary

ClinicalTracker.org records changes in ClinicalTrials.gov records and links the official source. Lindy can run a weekly agent that asks the tracker what changed on the trials you watch and sends a short, plain summary, so a family does not have to remember to check. Information only, not medical advice.

AgentStructure.AI5 min read

Works with

  • Muse.ai
  • Instinct
  • Grok
  • Claude
  • ChatGPT
  • Any MCP-capable assistant
Set a weekly Lindy agent to ask ClinicalTracker.org what changed on the trials you watch and send you a plain summary with the official links.
C
Example alert. Names and numbers are illustrative.

Key takeaways

The short version.

  • ClinicalTracker.org records the changes it observes in ClinicalTrials.gov records, such as a new status or a revised date, and links every change to the official record.
  • Lindy's documentation describes custom MCP servers added by a public HTTPS address, and routines that run daily, weekly or monthly, with a dry run to preview what would happen.
  • Lindy runs the weekly check and writes the summary. ClinicalTracker.org supplies the changes and the links. You read the official record and ask the study team your questions.
  • Nothing here is a listing or built-in integration with Lindy, and this setup has not been tested end to end. Whether the signed-in address works with Lindy is untested; the public search-only address is the fallback.
  • This is information only, not medical advice. The agent summarizes what changed; the family asks the study team or the doctor what it means.

Who it is for

Who is this pairing for?

  • It is for families, caregivers and patient advocates who follow a few clinical studies and would rather get one short note a week than…

  • ClinicalTracker.org watches ClinicalTrials.gov and openFDA, keeps a history of the changes it observes, such as a new status, a revised…

  • ClinicalTracker.org says what changed.

It is for families, caregivers and patient advocates who follow a few clinical studies and would rather get one short note a week than open a registry. It also suits research staff who want a regular digest for a shared watch list.

ClinicalTracker.org watches ClinicalTrials.gov and openFDA, keeps a history of the changes it observes, such as a new status, a revised date, a new site or posted results, and links each one to the official record. Lindy builds AI agents that run work automations on a schedule.

ClinicalTracker.org says what changed. A scheduled Lindy agent asks on your behalf and keeps the summary plain. Neither judges whether a trial is right for anyone.

Use cases

5 ways people use ClinicalTracker.org + Lindy.

  1. Weekly agent

    1. A weekly check on the trials you watch

    Lindy's routines page describes scheduled runs that are daily, weekly or monthly, and says a new routine defaults to 9:00 AM daily. Choose weekly and a day you will read it. Give the agent a plain instruction: for the trials on this list, ask ClinicalTracker.org what changed since last week, and tell me only if something did.

    Name the trials by their registry identifiers so the agent asks about the right ones.

  2. Plain summary

    2. One plain line per change

    A useful summary has one or two sentences per trial: what changed, from what to what, the date it was detected and the official link. Ask the agent to use only what the result says.

    A moved date is a moved date. Tell the agent not to guess what a change means for a person.

  3. Delivery

    3. Choose where the summary arrives

    Lindy's routines page names your Lindy chat, a text message (if your phone is verified), a Slack message and a phone call as ways a personal routine can reach you. It does not list email, and no Lindy page opened for this post confirms a scheduled agent can email you, so a listed channel is the safe choice.

    A dry run shows what the routine would have done without sending anything. The page notes that delivery itself is not tested by a dry run.

  4. No change

    4. Stay quiet when nothing changed

    Most weeks a watched trial may not change at all. Tell the agent to send nothing, or one line saying nothing changed, rather than filling the message.

    Use the dry run to see how the routine behaves on a quiet week.

  5. Questions to ask

    5. Turn a change into questions for the study team

    When a change appears, ask the agent to add two or three questions for the study site, for example whether a revised date affects the schedule or whether a new site is open to new participants.

    A registry status of recruiting is not a promise of an open place. The agent drafts the questions; the study team and the doctor answer them.

On your phone

What the alerts look like.

Illustrative

Figure 1

An example weekly summary. The trial, dates and sites are made up.

Example alerts. Every name, number and event shown is illustrative.

How to

How do I set up the weekly agent with Lindy?

  1. Step 1

    Copy the remote MCP address from [clinicaltracker.org](https://clinicaltracker.org): https://clinicaltracker.org/mcp (full tools, with sign-in) or https://clinicaltracker.org/mcp/public (search only).

  2. Step 2

    In Lindy, open Integrations, choose + Add, then MCP. Enter the server URL and a display name, then click Connect. Lindy's docs say a server with its own OAuth flow needs nothing extra in the dialog.

  3. Step 3

    If the signed-in address will not connect, use the public search-only address. Lindy's docs also allow a credential under Advanced, as a bearer token, custom header or query parameter.

  4. Step 4

    Under Guardrails choose Ask for approval or Always allow, and turn off any tool you do not need.

  5. Step 5

    Create a routine on a weekly schedule with your instruction and the trials to watch. Run a dry run, then pick a delivery channel.

Lindy describes custom MCP servers in its documentation, which does not say which plans include them. Delivery options are on its routines page. Whether ClinicalTracker.org's sign-in works with Lindy is untested, and the public address may offer fewer tools. Menus can change. ClinicalTracker.org is not listed by Lindy or built into it.

FAQ

Frequently asked questions.

Is ClinicalTracker.org an official Lindy integration?

No. There is no partnership, listing or built-in integration. Lindy lets you add a custom MCP server by its address, and you add the app's address yourself. The app is an AgentStructure.AI app.

Will the sign-in work with Lindy?

That is untested. Lindy's docs describe servers with their own OAuth flow, and static credentials under Advanced, but nobody has confirmed that ClinicalTracker.org's sign-in connects. The public search-only address is the fallback.

Can Lindy email me the summary?

That was not confirmed. Lindy's routines page lists Lindy chat, text message, Slack and a phone call for personal routines, not email. A listed channel works as a fallback today.

Is this medical advice?

No. ClinicalTracker.org reports what the official registries say and what changed. The agent only summarizes. Neither judges eligibility, ranks treatments or predicts whether a trial will succeed. Ask the study team or the doctor about any trial.

What does it cost?

The apps are free during the beta. Lindy has its own plans and credits, so check its pricing page.