flusterduck.com
Flusterduck monitors website behavior to detect user friction, score confusing pages, cluster issues, and verify whether deploys fix those problems. It focuses on behavioral signals rather than session replay or personal data collection.
Flusterduck exposes a REST API, a hosted MCP server, and a CLI; all require authentication, with secret/MCP keys for API and CLI use and OAuth sign-in for the hosted MCP server.
- Flusterduck MCP serverdetected
- Flusterduck REST APIdiscovered
- Flusterduck REST APIdeclared
- Flusterduck CLIdeclared
In the Flusterduck dashboard, go to Settings → API keys and create a secret key that starts with fd_sec_. Choose the scopes you need, such as query:read for reads and manage:write for writes. For terminal use, the easiest path is to run duck login or flusterduck login, which can open a browser, mint a key, verify it, and store it locally; FLUSTERDUCK_SECRET_KEY is the non-interactive fallback for CI.
In the Flusterduck dashboard, go to Settings → API keys and create an MCP key that starts with fd_mcp_. Use it for the local stdio MCP server; the hosted MCP server does not need a copied key. Pair it with your site ID in FLUSTERDUCK_MCP_KEY and FLUSTERDUCK_SITE_ID.
Point your MCP client at the server URL and approve access in the browser. The server accepts a Client ID Metadata Document (CIMD), so the client authenticates with its own hosted URL as the client_id — nothing to register.
conventions · 6/8 published
- integrations.json✓https://flusterduck.com/.well-known/integrations.json
- llms.txt✓https://flusterduck.com/llms.txt
- API catalog✓https://flusterduck.com/.well-known/api-catalog
- OpenAPI document✓https://flusterduck.com/openapi.json
- MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✓https://flusterduck.com
- Agent skills✓https://flusterduck.com/.well-known/agent-skills/index.json
Publish these signals → /publishing