Connect with a manual token

As an Admin, create a manual automation grant with the minimum scopes and expiry. Copy the token shown once into private client configuration. Do not give it to the assistant in chat.

This is a configuration fragment, not a command to execute:

{
  "mcpServers": {
    "pingstack": {
      "type": "http",
      "url": "https://pingstack.io/mcp",
      "headers": {
        "Authorization": "Bearer REPLACE_LOCALLY_WITH_MANUAL_TOKEN"
      }
    }
  }
}

Merge into the client’s existing private configuration, preserving other servers and settings. Replace the placeholder locally. Protect files with owner-only access and do not commit real tokens in project configuration.

Reload/restart the client and request capabilities. If the intended account or scopes are wrong, correct the grant before permitting writes.

Lifecycle

Manual grants expire within 90 days. Rotate in Pingstack settings and replace the old token everywhere it was used; old credentials stop working. Revoke when the integration is retired or its environment is compromised.

A manual bearer is not an OAuth client ID or secret. Do not combine manual headers with a browser OAuth entry and expect automatic token refresh.

See client-specific setup for Copilot, Claude Code and Claude Desktop. Client configuration conventions are not interchangeable.