Connect an AI assistant with MCP

Pingstack’s Model Context Protocol server lets an assistant inspect monitoring and perform explicitly permitted configuration work. Its endpoint is the hosted app origin plus /mcp, normally https://pingstack.io/mcp. Do not connect to the documentation host.

Choose HTTP / Streamable HTTP, not legacy SSE. The server is stateless and returns JSON responses to POST requests. It does not offer a persistent GET event stream or subscriptions; GET and DELETE receive method-not-allowed.

Choose authentication

Use browser sign-in when offered by your hosted account and supported by the client. The client handles OAuth without asking you to copy a bearer token.

For clients without compatible browser sign-in, use a manual grant. The same manual grant can authorize REST, while OAuth access tokens are audience-bound to MCP.

An Admin approves/manages connections. The connection remains limited by its selected scopes and the approving user’s current account role. Tool discovery shows only operations whose primary scope is permitted; an advertised write can still require additional assignment scopes.

Start read-only

After connecting, request account capabilities and a check list. Verify the account identity before allowing writes. Then review tool arguments and boundaries and example workflows.

MCP is an interface to your account, not autonomous permission to publish a status page, initiate a purchase or expose credentials. Review proposed changes before running write tools.