Is there a meertrack MCP server?

You don't need an MCP server to give your agent meertrack. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, which keeps another server's tool definitions out of your agent's context.

Can I limit what my agent is allowed to do with the meertrack API?

Yes. Every meertrack operation is a read, so the useful limit is which data the agent sees. For example, write a rule that allows only GET /digests/latest, so a briefing agent can read each competitor's latest digest but not the raw activity feed or item detail. Every call it makes is logged.

What are the rate limits for the meertrack API?

The spec states a limit of 60 requests per minute per workspace, enforced per serverless instance, so X-RateLimit-Remaining is not monotonic across requests. Treat a rate-limited response with X-RateLimit-Reset as the backoff signal and add jitter.

How do I get only recent changes instead of the whole roster?

Pass from, and optionally to, on GET /activity. With a window you get adds, updates, and removals in that period only. Omit both and you get the complete all-time roster, including items that existed when tracking began, so change_type=added then covers nearly everything.

How do I pull competitor changes with meertrack through Jentic?

Search Jentic for an intent like 'see what competitors changed this week', import the meertrack API, and store your key once. Your agent then calls GET /activity with a from date and the sections it cares about, and GET /activity/items to resolve the details. To run it on your own infrastructure, install Jentic One from its GitHub repo.