Every Checky installation includes a remote MCP server at https://<your-host>/mcp (Streamable HTTP,
OAuth 2.1). ChatGPT and Claude connect to it; people sign in with their normal Checky account and approve access.
Nothing to install, no API key to copy.
Requirements: a public https:// BASE_URL, with /mcp, /.well-known/* and /api/auth/* reachable from the
internet (not behind basic auth or a VPN).
Claude
Claude (web, Desktop, mobile): Settings → Connectors → Add custom connector, URL https://<your-host>/mcp,
leave the OAuth fields empty, Connect. Sign in to Checky and allow access. Enable the connector in a chat.
Claude Code:
claude mcp add --transport http checky https://<your-host>/mcpThen run /mcp and authenticate.
If you filter inbound traffic, allow Claude’s range 160.79.104.0/21 for /mcp, /.well-known/* and
/api/auth/*.
ChatGPT
Settings → Apps & Connectors → Advanced → Developer mode on, then Create a connector: URL
https://<your-host>/mcp, authentication OAuth. ChatGPT discovers everything itself; sign in to Checky and
allow access.
What you can ask
- “What do I need to answer today?” — shows today’s check-ins (with an interactive widget).
- “Answer yes to the backup check.” / “I’m sick tomorrow.”
- Admins: “Who hasn’t answered today?”, “Summarise my team’s last week”, KPI trends, create checks.
Answers given through ChatGPT/Claude count like any other answer (channel mcp). Texts come back in the
member’s language. Wellbeing answers are never shown per person — only anonymous aggregates with enough
respondents.
Access and revocation
Members see only what they see in the app; admin tools need the admin role. Write tools need the write permission granted at the consent screen. To revoke access, remove the connector in ChatGPT/Claude or revoke the consent in Checky.
OAUTH_CIMD=true (default) lets ChatGPT and Claude identify themselves with Client ID Metadata Documents;
dynamic client registration works as a fallback.