Connect your AI agent
Avospy ships a native MCP server. Connect it once and your AI assistant can add sites, read live uptime and pull your weekly report — in plain language, without opening the dashboard.
1. Create an access token
Sign in and open Settings → AI / MCP Access, then click New Token. Name it after the client that will use it — “Claude Desktop”, “Cursor”, “CI” — so you can tell them apart later.
- Tokens start with avospy_mcp_ and are shown exactly once — copy the value right away.
- Only a SHA-256 hash is stored, so a lost token cannot be recovered; create a new one instead.
- A token carries the full access of your account. Issue one per client so you can revoke them separately.
2. Point your client at the endpoint
The server speaks Streamable HTTP and authenticates with a bearer token. That is all your client needs:
https://avospy.com/api/mcpStreamable HTTPAuthorization: Bearer avospy_mcp_…claude mcp add --transport http avospy https://avospy.com/api/mcp \
--header "Authorization: Bearer avospy_mcp_YOUR_TOKEN"{
"mcpServers": {
"avospy": {
"type": "http",
"url": "https://avospy.com/api/mcp",
"headers": {
"Authorization": "Bearer avospy_mcp_YOUR_TOKEN"
}
}
}
}Not sure whether the token works? Call the endpoint directly — a valid token answers with a JSON-RPC listing of the tools below, an invalid or revoked one returns 401 Unauthorized.
curl -i https://avospy.com/api/mcp \
-H "Authorization: Bearer avospy_mcp_YOUR_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'The reply arrives as an “event: message” line with a JSON-RPC payload — that is normal for Streamable HTTP, not an error.
3. Just ask
Once the client is connected, the tools show up in the conversation. You do not call them by name — describe what you want:
4. What the agent can do
Six tools, all scoped to your own account. Plan limits apply exactly as they do in the dashboard.
| Tool | What it does | Arguments |
|---|---|---|
list_projects | Every project in your account with its latest uptime check. | none |
add_project | Adds a website. Uptime, SSL, DNS, SEO and performance checks start automatically. | name, url |
get_project | One project in detail: latest check, SSL status and a 7-day uptime summary. | projectId |
configure_project | Rename a project, change its URL, or pause and resume monitoring. | projectId, name?, url?, active? |
get_uptime | Day-by-day uptime and response times for the last 1–90 days (7 by default). | projectId, days? |
get_report | Your latest weekly report — generated on the spot if none exists yet. | none |
5. Keeping the token safe
- Treat the token like a password: keep it in an environment variable or a secret manager, never in a committed config file.
- Revoking a token in Settings takes effect immediately — the next request is rejected.
- Each token shows when it was last used, so an unused one is safe to delete.
- The endpoint is HTTPS-only and every request without a valid token is answered with 401.
6. When something does not work
401 Unauthorized
The token is mistyped or revoked, the header is missing the “Bearer ” prefix, or the value does not start with avospy_mcp_.
The client hangs while connecting
It is probably trying the legacy SSE transport. This server speaks Streamable HTTP only — set the transport type to “http”.
“Project not found (or not owned by you).”
The projectId belongs to a different account, or it is a name instead of an id. Run list_projects first and reuse the id from there.
“Project limit reached”
You hit the project quota of your plan. Change the plan in Billing, or pause a project you no longer need.
Uptime data comes back empty
Monitoring has just started. The first checks arrive within a few minutes; daily statistics appear after the first full day.
Still stuck? Write to support@avospy.com and include the name of your MCP client.
Ready to connect your agent?
Create an account, add your first site, and issue a token — all in a couple of minutes.