flowsery.yaml 1.7 KB

123456789101112131415161718
  1. name: flowsery
  2. title: Flowsery
  3. repo: https://github.com/Flowsery/claude-plugin
  4. sha: 5f6866b19e1ebd1ccb6561a1fdb64b763a76876e
  5. version: "1.3.1"
  6. description: "Privacy-first web analytics through Flowsery's hosted MCP server (Streamable HTTP at https://mcp.flowsery.com/mcp, OAuth sign-in, no keys in config): visitors, sessions, bounce rate, time series, real-time visitors, breakdowns by page, referrer, channel, campaign, country and device, goals and revenue attribution, single visitor journeys, and the bugs and UX problems Flowsery found in session recordings. Bundles the flowsery workflow skill. Agent Plugins v1 package (plugin.json + mcp.json + skills/), configuration only. Disclosure — every tool call goes to Flowsery's hosted server (mcp.flowsery.com) and acts on the user's Flowsery account with their own workspace role; the tool set is served by that server at runtime and is not covered by the pinned sha. Most tools are read-only; track_goal and track_payment record goal and payment events in the user's analytics (no money moves), delete_goals and delete_payments permanently remove those events, and update_issue_status changes an issue. Sign-in runs the pinned mcp-remote@0.1.49 through npx (Node.js 20.18.1+ and npm required), which opens a browser and a local callback port on first use and stores OAuth tokens under ~/.mcp-auth. The package marks the server untrusted, so Hermes asks before every tool the server does not mark read-only and refuses them in unattended runs."
  7. maintainer: Flowsery
  8. tier: community
  9. category: tools
  10. docs_url: https://github.com/Flowsery/claude-plugin#install-in-hermes-agent
  11. requires_hermes: ">=0.21.6"
  12. readme: true
  13. platforms: []
  14. capabilities:
  15. provides_tools: []
  16. provides_hooks: []
  17. provides_middleware: []
  18. requires_env: []