MCP toolsRead and fixUpdated
What happened lately
What does mttr_events do?
The newest things that happened: reads asked for, finished and failed, scores that moved, and rules that were fixed. Only whoever runs this mttr may make this call.
When to use it
- You come back after a while and want to catch up.
What you ask
You say“What has happened on mttr since this morning?”
Your assistant calls
mttr_events({})| Argument | Type | Needed | What it is |
|---|---|---|---|
site | Text | No | Only events for this site. |
limit | Number | No | How many to return. |
What comes back
- Each event with its time, its site and what happened.
| When | Site | What happened |
|---|---|---|
| 11:20 | example.com | Score 64 to 72 |
| 11:18 | example.com | Read finished |
| 11:09 | example.com | Read asked for |
Made-up sites and figures, to show the shape of the answer. The answer itself is JSON.
Over HTTP
It is GET /api/v1/events, with your key as a bearer token:
curl "https://mttr.si/api/v1/events" \
-H "Authorization: Bearer $MTTR_KEY"When it fails
| When | Status | What to do |
|---|---|---|
| Your assistant has no key yet | 401 over MCP | Sign up with mttr_signup, then connect again with the key it gives. |
| The key is a person’s, not the owner’s | 403 | Nothing: only whoever runs mttr makes this call. |
Every error’s wording is in the API reference.
The call in full, with its HTTP address, each argument’s type, who may make it and the call in four languages, is mttr_events in the API reference.