SentryDock MCP server: connect any compatible agent
By Blake Folgado · Updated 2026-10-03
Model Context Protocol lets an assistant discover tools and call them through a remote server. SentryDock exposes the same news and monitoring account through streamable HTTP MCP. Use the client setup guide for its configuration format; JSON for Cursor is different from a Codex terminal command.
Use OAuth at the public /mcp endpoint when your client supports it. API keys created in Settings → Agents provide a second authentication route. Treat a key-bearing URL as a credential and never publish it in a repository.
The workflow
- Choose one of the client guides on the agent hub.
- Add https://www.sentrydock.com/mcp as a remote HTTP server.
- Finish OAuth with your SentryDock account and enable its tools for the session.
- Call account.overview, then news.search with an explicit time window and inspect the returned source links.
https://www.sentrydock.com/mcp{
"mcpServers": {
"sentrydock": {
"url": "https://www.sentrydock.com/mcp"
}
}
}Tools for research and monitoring
- account.overview — your plan, monitors, delivery and recent alerts.
- news.search and news.latest — source-linked indexed items.
- news.mine, news.get and alerts.list — account hits and individual evidence.
- monitors.list, monitors.create, monitors.update and monitors.run — inspect and manage monitoring.
- monitors.runs and monitors.results — inspect execution and output.
- delivery.connect — attach an authorised delivery destination.
Authentication, cost and plan limits
The connection acts on your account. Overview and usage can be read before payment; news and monitoring need plan access. A plan_required response includes a pricing URL. Monitor limits and supported realtime slots follow the same plan as the app.
Inspect the live tool schema before writing; confirmation requirements apply to consequential changes. A connection does not authorise a new subscription, a team invitation or a destination you have not chosen.
Can any MCP client use it?
The client must support a remote HTTP server and an authentication method the gateway accepts. An application that only loads local stdio servers needs its own documented remote bridge. Start with the confirmed guides rather than pasting a URL into an unrelated plugin marketplace.
Reference and troubleshooting
API guide · HTTP schema · Account settings · All client guides.
If tools are missing, check transport, login, per-conversation enablement and workspace policy. A successful account response is the first useful check; a 200 response from a public website alone is not an authenticated MCP test.