MCP server

1Tools

list_issues {status?, limit (1 to 50, default 20), query? (text in the title)}: id, status, level, event count, last seen, last release, title. get_issue {id}: counts, first and last seen, release, regressions, companies, and the latest event's stack trace with in-app frames marked, the last 10 breadcrumbs and the request URL without its query string. resolve_issue {id}, ignore_issue {id}, reopen_issue {id}. list_monitors {}: the workspace's monitors and heartbeats with status, last check and 24-hour uptime. get_ai_fix {id}: the latest finished AI analysis (summary, cause, fix).

2Errors and limits

401 for no or unknown key, 403 for a public key. GET answers 405. Bodies over 256 KB get 413; batches are refused. 300 requests a minute per key. Any text that came from events is wrapped in <untrusted-data> blocks so the agent treats it as data, not instructions.

curl https://in.blipit.io/mcp \
  -H "Content-Type: application/json" -H "Authorization: Bearer <secret key>" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_issues","arguments":{"status":"unresolved","limit":5}}}'

Good to know

• Issue ids from another project answer 'not found' for reads and writes alike.
• No instance header is needed, even for Odoo projects.