Skip to content

Add data/flowsery: Flowsery site analyst - #66

Open
TarasShyn wants to merge 2 commits into
nanocoai:mainfrom
TarasShyn:add-flowsery-template
Open

TarasShyn wants to merge 2 commits into
nanocoai:mainfrom
TarasShyn:add-flowsery-template

Conversation

@TarasShyn

Copy link
Copy Markdown

What this template does

A site analyst for the user's websites. It answers traffic and revenue questions from Flowsery's web analytics (sources, channels, campaigns, pages, geography, devices, goals, conversion rate, revenue, live visitors) and reports what is broken: the bugs, broken flows and UX problems Flowsery's AI found in real session recordings, ranked by sessions affected. It can set issue status and, after an explicit "yes", record or delete goals and payments.

  • MCP: one streamable-http server, https://mcp.flowsery.com/mcp, hosted by Flowsery. Nothing runs locally.
  • Skills: flowsery (operating logic, with references for report shapes, writes, credentials and onboarding) and welcome.
  • Task: weekly-health-report.md, Mondays 9 AM, read only, ships paused.
  • Personal data: visitor profiles and payments can hold names and emails. The brief limits profile lookups to explicit asks and keeps them out of reports.

Disclosure: I'm the founder of Flowsery, the paid service this template connects to. The README says so up front; users bring their own key, and no credential, referral link or billing ships in the template.

Category: data, next to data/analyst. Happy to move it to product if you'd rather.

Where it lives

data/flowsery/

Services and credentials

See Connect your Flowsery key in the template README: API host mcp.flowsery.com, Authorization: Bearer injected by OneCLI, the role the key needs (Editor or Admin; keys carry a workspace role, not scopes), and the plan note (both plans include every feature; 14-day trial, during which only the first ten issues open in full).

Validation

  • node scripts/check-templates.mjs -> OK
  • node scripts/build-index.mjs then git diff --exit-code index.json -> clean
  • NanoClaw parseTemplate + prepareTemplateTasks (main @ d4ff64f4) on the folder -> empty skip report, 2 skills, 1 MCP server, 1 task with a valid cron
  • Unauthenticated POST https://mcp.flowsery.com/mcp -> 401 with WWW-Authenticate: Bearer resource_metadata=...; the server takes a plain API key as Authorization: Bearer, which is what OneCLI injects
  • Not stamped in a live NanoClaw install. The same hosted MCP server and tool set are in production use from Claude, Cursor, ChatGPT and our OpenClaw plugin; the NanoClaw-specific part is OneCLI injecting Authorization: Bearer for mcp.flowsery.com, the same path feat: add PostOnce social media template #61 exercised for a streamable-http server

Before you open this

  • node scripts/build-index.mjs run and the regenerated index.json committed
  • node scripts/check-templates.mjs passes
  • New template, so no version bump needed
  • No secrets anywhere in the diff
  • Read Acceptance and ownership and the full PR checklist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant