Ask Your Traffic Questions Through a Manus Cue Connector for Web Analytics

Cue, the personal-agent app Manus launched on 28 September 2026, answers traffic questions once you give it a Manus Cue connector for web analytics, and the documented way to build one runs through Manus rather than through Cue. Manus says Cue is "built on the same infrastructure as Manus", and Manus has a proper form for adding an MCP server. Cue, as of 29 September 2026, has no connector documentation of its own.

The short version: add https://mcp.flowsery.com/mcp in Manus under Settings, Integrations, Custom MCP Servers, Add Server, with a flow_ws_ workspace token created under the Contributor role. Then ask your Cue agent to list your websites. That call reads and writes nothing.

What is a Manus Cue connector?

A Manus Cue connector is a link between a Cue agent and an outside service, and "connector" is Manus's own word for it. Manus's help centre describes connectors as "a user-centric integration layer that enables Manus to securely access your third-party data and APIs (including MCP servers)", and it names two kinds you build yourself: a custom API connector and a custom MCP connector.

Cue itself is new. Manus calls it "a new standalone app for your personal agents, on your phone and desktop", and each agent in it gets its own email address, phone number, wallet and computer. Manus has published no Cue page about connectors, MCP, credential storage or approvals as of 29 September 2026. Runtimewire noted the same gap on launch day: the announcement "does not explain in detail how users approve individual transactions".

That gap shapes everything below. Where Manus documents a step, this guide gives you the menu path. Where Cue is silent, it gives you a test.

Where do you add the Flowsery MCP server?

Manus takes custom MCP servers under Settings, Integrations, Custom MCP Servers, Add Server, and the form asks for three things. Manus then checks that it can reach the server and pulls the list of tools the server offers.

Flowsery's MCP server accepts two kinds of sign-in. MCP clients that support OAuth open a browser and sign you in with no key to paste. Clients without OAuth send an Authorization: Bearer header with a token from the API Tokens page, and Manus's documented field asks for exactly that: "API key, Bearer token, or other credentials required". Use the Bearer route.

Manus also says a service with a well-documented REST API sometimes needs no MCP server at all, because Manus can call the API directly. Flowsery publishes its full spec at https://flowsery.com/openapi.json with every endpoint under https://analytics.flowsery.com/analytics/api/v1. The MCP server is the cleaner route, since Manus lists its tools for you and you see exactly what the agent can call.

How do you get the connector into Cue?

Cue has no documented connector menu, so you add the server in Manus and, if Cue does not see it, ask your Cue agent in chat to add Flowsery as a custom MCP connector. Manus documents neither step for Cue, which is why each ends in a read call you check. Manus has not said whether a connector added in the Manus web app carries over into Cue automatically. Try the Manus form first, open Cue, and ask for your website list. If the agent answers with real website names, the connector carried over. If it asks what Flowsery is, paste this:

Add Flowsery as a custom MCP connector.
Server URL: https://mcp.flowsery.com/mcp
Auth: Authorization: Bearer <token>. The token starts with flow_ws_.
Ask me for the token in a credential field if you have one. If you only
have this chat, tell me where the token will be stored before I send it.
 
Then call list_websites and show me the website names and IDs.
Do not call any tool that records, deletes or updates data.

The credential lines matter. Manus redacts "sensitive information like API keys" when a Manus session is shared, and says removing a connector clears "all login information and saved credentials". Cue's own handling of a secret typed into a chat is undocumented. A token that the agent is going to hold anyway is less exposed in a credential field than in a transcript, so ask before you paste.

Which Flowsery token should a Cue agent hold?

A Cue agent should hold a flow_ws_ workspace token issued under the Contributor role, which Flowsery marks "Recommended for AI agents" in the Create Token form. Flowsery's team settings describe Contributor as "Same access as Viewer here" and Viewer as "Sees everything, changes nothing". The token inherits that ceiling: "Requests with this key are limited to what a Contributor can do, and to what you can do."

This is the approval gate Cue does not document. Flowsery's writes need the flowsery.write permission, which only Admin and Editor hold, and any other role gets 403 permission_denied on a write. The agent cannot talk its way past a role. Set an expiry date in the same form, and revoke the token from the same page the day you stop using Cue.

A workspace token reaches every website in its workspace. If one client's site is off limits, put it in a different workspace, because a websiteId filter in your prompt is a request, and the role is a rule.

Which Flowsery calls read, and which ones write?

Flowsery's public API spec lists 28 operations as of 29 September 2026, and 23 of them only read. Five change data. The MCP server exposes the same split, and Manus shows you the tool names when it fetches the list.

A Contributor token turns all five writes into a 403. That is the right default for anything you ask from a phone. Nobody needs an agent recording a payment because a sentence in a chat sounded like an instruction.

What changes when the agent has its own email and computer?

A Cue agent can act on your analytics numbers outside the chat, because Manus gives each agent "its own email, phone number, wallet, and computer, so it can send messages". A Claude or ChatGPT session answers you. A Cue agent can email your traffic figures to someone else, and Manus has not documented a way to restrict what an agent does with its email or phone identity.

Two rules cover it. Name the recipients of any report in the prompt, and keep visitor-level data out of email. GET /visitors/{visitorId} returns a profile block with userId, name and email for visitors your site has identified, and that belongs in the chat with you, not in an outbox.

The agent's computer is the other half. An MCP call loads no page and fires no tracker, so questions asked through the connector leave your numbers untouched. Asking the agent to "go look at the pricing page" on its own machine loads the page like any browser, and that visit lands in your analytics. Ask through the connector.

Group chats add a third wrinkle. Agents in a Cue group chat share a goal and "hand work to each other", with you making "the final call". Give the Flowsery connector to one agent in the group and let the others work from its answers. The analytics reporting guide builds a two-agent weekly report on that split, and the session analysis guide does the same for issue triage.

Who can use Cue, and what does it cost?

Cue is in invite-only early access and free to use as of 29 September 2026. Manus's launch post says you "can start with MEETCUE", a code available to a limited number of early users first come, first served, and everyone admitted gets extra invite codes. Manus has not said what Cue costs after early access.

Manus lists Cue on web, desktop and mobile, with iOS waiting on App Store review. Inside Manus, the Agents (Cue!) tab in the sidebar shows a QR code for the app download.

The Flowsery side has two plans, and both include the API and MCP server. Team costs $250 a month with 5 team members and 2 websites. Pro costs $500 a month with 10 team members and unlimited websites. Both start with a 14-day free trial and no card. If you already read the Meta Muse connector for web analytics guide, the difference is the MCP form: Muse had no field for an MCP server, and Manus documents one. InfoWorld framed Cue as a rival to Meta's Muse on 29 September 2026, and Manus has run independently of Meta since 1 September 2026. The Grok bot template for web analytics is the option with the skill text already written.

Frequently Asked Questions

Does Cue support MCP servers?

Manus supports custom MCP servers under Settings, Integrations, Custom MCP Servers, and Cue runs on the same infrastructure. Manus has not documented a Cue screen for MCP as of 29 September 2026. Add the server in Manus, then confirm inside Cue by asking the agent to list your Flowsery websites.

Can I sign in to Flowsery with OAuth instead of a token?

Flowsery's MCP server supports OAuth sign-in for clients that open a browser. Manus's documented custom MCP form asks for an API key or Bearer token, so the Manus route uses a flow_ws_ token today. Create it under the Contributor role so the connector reads and never writes.

Can a Cue agent change my Flowsery data?

A Cue agent holding a Contributor token cannot change anything. The five Flowsery writes cover goals, payments and issue status, and all five need the flowsery.write permission that only Admin and Editor hold. A Contributor token gets 403 permission_denied on every one.

Why does the agent fail on a website it can see?

A workspace token covers every website in the workspace, so each call needs websiteId or domain. Flowsery's API reference lists a workspace token without a selector under 400 Bad Request. Tell the agent to call list_websites first and carry the ID through every call.

How do I cut a Cue agent off from my analytics?

Revoke the token at flowsery.com/api-tokens, and every app using it loses access at once. Removing the connector in Manus also clears its saved credentials, according to Manus's connector help article. Revoking on the Flowsery side works whatever Cue has stored.

Is Cue available outside the United States?

Manus has published no country list for Cue as of 29 September 2026. Access depends on an invite code, and Manus says agent phone numbers work only in select countries for now. Try the MEETCUE code and check whether the app admits you.

How do I get into Cue?

Cue is in invite-only early access. Manus says you can start with the MEETCUE code, which is available to a limited number of early users first come, first served. Everyone admitted gets extra invite codes.

What should I ask a Cue agent first?

Ask it to list your websites, then ask for last week's overview against the week before, with timezone Europe/Berlin. Both are reads, so nothing gets written. If the second call fails, tell the agent to carry the website ID from the first.

How much does Flowsery cost?

Team costs $250 a month with 5 team members and 2 websites. Pro costs $500 a month with 10 team members and unlimited websites. Both include the API and MCP server, and both start with a 14-day free trial and no card.

Can a Cue agent email my visitor data?

Manus has not documented a way to restrict what an agent does with its email identity. GET /visitors/{visitorId} returns a profile block with userId, name and email for identified visitors. Keep that data in the chat with you, and name the recipients of any report in the prompt.

Create a Contributor token at flowsery.com/api-tokens, add the server in Manus, and ask Cue for last week's traffic. For the numbers side of Flowsery, start at the web analytics dashboard.

Sources: Introducing Manus 2.0 (28 September 2026), What is new in Manus 2.0, How can I use Manus Connectors?, Manus custom MCP docs, Manus resumes independent operations, Runtimewire (28 September 2026), the Flowsery OpenAPI spec and the Flowsery API reference. Checked 29 September 2026.