Mora AI MCP server

Mora AI

Codex guesses your brand voice. Mora AI gives it the real one, plus your real catalogue and performance.

What is Mora AI

Mora serves solo creators and small teams building an audience or a brand, not only stores. That covers a Shopify or DTC operator who wants a product named correctly instead of invented, a coach or speaker building a personal brand on LinkedIn with no catalogue at all, and a full-time creator posting daily across three platforms. Mora also has a franchise tier for multi-location owners and an enterprise tier for organizations running governed brand templates. It plans, drafts, gets human approval, schedules and publishes content, and closes the loop with real engagement and, for connected Shopify stores, revenue attribution. What Mora does that a generic content tool doesn't: it grounds every draft in the account's own real data, not a brand-voice guess.

Who this plugin is for: a user of a supported MCP host who already has (or wants) a Mora account and wants to pull their own brand context, past performance, and product catalogue into an agent session — for example, to plan a Product Hunt launch, draft a week of posts, or check what already worked before writing more.

What this plugin gives you

paste. First use triggers Mora's own OAuth 2.1 consent screen in your browser. The hosted MCP runtime and account-scoped handlers live in Mora's product app; this public repository contains only connector configuration and workflow skills.

• Mora AI's official remote MCP server connector, pre-configured — no manual .mcp.json editing, no API key to

listproducts, getrevenueattribution, listprojects, listaudiences, listcontentangles, listbriefruns, and getpaidcampaignperformance — Google, Meta, and LinkedIn Ads campaign delivery as each platform reports it. That last tool needs a separate mora.read.ads consent: a new connection asks only for mora.read, and the first time an agent calls the ads tool, Mora asks the account owner to approve ad reporting on its own consent line. No tool can publish, schedule, connect an account, change an ad account, or spend money — Mora treats writes through an unattended agent loop as unsafe to expose.

• Read-only tools: listposts, getpostperformance, getbrandprofile, getbrief_workspace,

writes stays on-brand, without re-fetching it per message.

• A brand-voice resource (mora://brand/voice) you can attach once per session so every message Claude

writelikewhat_worked — most notably a full Product Hunt launch week that already knows Product Hunt's current rules (no vote solicitation, no "Coming Soon" pages — retired August 2025) so you don't have to.

• Three launch-workflow prompts — producthuntlaunchweek, firstmaker_comment, and

chain tool calls yourself:

• Six skills that package the tools above into actual workflows instead of leaving you to

you ask about connecting to or using Mora.

• skills/mora-mcp-setup — first connection, what each tool and prompt is for. Triggers when

synthesized brief on what's actually working (platform, theme, timing) and what to do next. Triggers on "how is my content performing", "audit my Mora posts", "what's working on my social".

• skills/content-performance-audit — combines listposts and getpost_performance into a

factual brand + catalogue summary for work happening outside Mora — briefing a designer, writing ad copy, prepping a pitch. Triggers on "give me my Mora brand brief", "what does my brand sell", "summarize my Mora catalogue".

• skills/brand-brief — combines getbrandprofile and list_products into a portable,

planned against what's actually gone out and surface overdue or orphaned content. Triggers on "check my Mora content

• skills/content-gap-check — combines listprojects and listposts to compare what's

Shortened. The full README is on GitHub.