Pulse on Studio canvas

Pulse connects your X (Twitter) timeline to Majico so you can see top posts, draft tweets with brand context, and (via Cursor MCP) let an agent summarize engagement on your Studio canvas.

Published docs: https://docs.majico.xyz/pulse/

What you need

A Majico project with guidelines (product name, tone, palette).
Pulse linked to that project — creates or attaches a Pulse organization.
Optional: X account synced in Pulse so widgets show real metrics (not empty state).

Link Pulse to a project

From the app (session auth):


POST /api/projects/{projectId}/pulse
Content-Type: application/json
 
{ "name": "My brand Pulse org" }

Response includes organizationId. The project stores pulse_organization_id for canvas widgets and MCP.

Check status:


GET /api/projects/{projectId}/pulse

Canvas widgets

On the Studio canvas, ask the agent to add a top posts widget or add a widgetFrame with kind: "top-posts". The card loads live data from:


GET /api/projects/{projectId}/pulse/posts?sort=best&limit=5

Widget kind	Purpose
`top-posts`	Best posts by engagement
`tweet-draft`	Selected tweet draft from MCP
`pulse-stats`	Org sync health (coming soon)

Empty states prompt you to link Pulse or sync X — widgets never show fake sample metrics.

Cursor MCP (Pro)

Agents use the same list → choose → persist pattern as logos and palettes:

Tool	When to use
`get_pulse_status`	Is Pulse linked? How many X accounts?
`list_pulse_posts`	Summarize top posts (read-only)
`generate_tweet_drafts`	Returns 2–3 variants — user must pick
`select_tweet_draft`	Writes draft to canvas + `tweet_draft_selected` handoff

Open browserPulseUrl from bootstrap_project (/canvas?project=…&pulse=1&cursor=1) in Cursor Glass for browser handoff.

Agents must not auto-pick tweet variants when multiple drafts exist.

Hosting

User-facing Majico docs (this site) are served at https://docs.majico.xyz from the homelab Kubernetes cluster (majico-docs deployment, NodePort 30081, edge nginx). Staging app (majico.d3bu7.com) and production app (majico.xyz) both link here.

After each staging deploy, scripts/staging/deploy.sh rebuilds and rollouts docs when DEPLOY_DOCS=true (default).

See also: Cursor MCP integration · Studio canvas