Mora AI

io.github.Mora-AI-Content-StudioPublished by GitHub account Mora-AI-Content-Studiov1.0.3Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Mora AI is a remote, read-only MCP connector that gives an assistant a creator's real brand profile, product catalogue, post performance and ad data for…

What you can do
  • Read posts and their performance, plus paid campaign delivery from Google, Meta and LinkedIn Ads
  • Read the brand profile, brief workspace, projects, audiences and content angles
  • Read the product catalogue and Shopify revenue attribution
  • Attach a brand-voice resource once per session so drafts stay on-brand
  • Run launch-workflow prompts such as a Product Hunt launch week, a first maker comment, or writing from what already worked
  • Use bundled skills for performance audits, brand briefs, content-gap checks, paid-ad copy and campaign plans
When to use it
For creators, coaches and small teams who already use Mora and want an agent session to plan launches, draft posts or ad copy, or check what content already performed, using their own account data instead of guessed brand voice.
Requirements
A remote endpoint at app.mora-marketer.com; no local package or API key. An existing or new Mora account is required, and every request needs an OAuth-issued bearer token obtained through Mora's consent screen. The server uses CIMD client identification, so the README lists Claude Code as supported, Claude Desktop as expected but unverified, and Codex CLI, Cursor, VS Code and Windsurf as not yet supported.
Before you install
Access is read-only: no tool can publish, schedule, connect an account, change an ad account or spend money. The ads tool needs a separate mora.read.ads consent beyond the initial mora.read scope, so the account owner is asked to approve ad reporting. Account data such as brand profile, catalogue, performance and revenue attribution is sent to the connected assistant session.

Installation

In SourceWeft

  1. Open Mora AI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Mora-AI-Content-Studio%2Fmora/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "mora-ai": {
      "type": "http",
      "url": "https://app.mora-marketer.com/api/mcp"
    }
  }
}

README

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

  • Mora AI's official remote MCP server connector, pre-configured — no manual .mcp.json editing, no API key to 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.
  • Read-only tools: list_posts, get_post_performance, get_brand_profile, get_brief_workspace, list_products, get_revenue_attribution, list_projects, list_audiences, list_content_angles, list_brief_runs, and get_paid_campaign_performance — 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.
  • A brand-voice resource (mora://brand/voice) you can attach once per session so every message Claude writes stays on-brand, without re-fetching it per message.
  • Three launch-workflow prompts — product_hunt_launch_week, first_maker_comment, and write_like_what_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.
  • Six skills that package the tools above into actual workflows instead of leaving you to chain tool calls yourself:
    • skills/mora-mcp-setup — first connection, what each tool and prompt is for. Triggers when you ask about connecting to or using Mora.
    • skills/content-performance-audit — combines list_posts and get_post_performance into a 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/brand-brief — combines get_brand_profile and list_products into a portable, 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/content-gap-check — combines list_projects and list_posts to compare what's planned against what's actually gone out and surface overdue or orphaned content. Triggers on "check my Mora content calendar for gaps", "am I behind on my content schedule".
    • skills/paid-ad-copy — turns real brand, catalogue, audience, angle, and performance data into paid-ad copy and a human-reviewable test matrix. It never creates campaigns or spends money.
    • skills/campaign-plan — turns existing plans, posts, audiences, angles, catalogue facts, and performance into a grounded campaign plan without scheduling or publishing anything.

Why read-only, and why so few tools

Read-only is a considered position, not a placeholder. Every serious content-quality failure Mora has shipped and documented — a fabricated brand wordmark reaching a draft, unrequested posts silently added to an account — happened with a human reviewing the loop. Handing write access to a loop without one isn't something Mora can honestly call safe yet.

A small tool count is a measured ceiling, not an economy move: published research on tool-selection accuracy shows smaller models' tool-choice accuracy degrading past roughly 10–15 tools in a single context, and Mora's own design principle is that a longer tool list is not automatically better for an agent holding it. These answer the questions a marketing agent actually asks — including "what real revenue does a channel actually deserve credit for", "which audience is this for", and "which content angles or brief findings already exist" — and nothing here overlaps.

Requirements

  • An existing or new Mora account (free to create at https://www.mora-marketer.com).
  • Claude Code with plugin support and remote MCP + OAuth support enabled.

Contract and runtime ownership

The canonical remote MCP endpoint is https://app.mora-marketer.com/api/mcp. The live server card at https://app.mora-marketer.com/.well-known/mcp/server-card.json is the source of truth for the tool, resource, prompt, and read-only metadata. This public repository is the Claude Code connector and workflow package; it is not the private MCP runtime. Repository: https://github.com/Mora-AI-Content-Studio/mora-claude-plugin.

Run the production contract check before publishing documentation changes:

bash
node scripts/check-mora-mcp-contract.mjs

For an offline fixture, set MORA_MCP_SERVER_CARD_FILE=/path/to/server-card.json.

Developer documentation:

Authentication and client compatibility

Every request needs an OAuth-issued bearer token. Mora's server identifies clients with CIMD (Client ID Metadata Documents) — the MCP spec's current recommended standard (2026-07-28), which formally deprecates the older Dynamic Client Registration (DCR) flow. Claude's own SDKs and Claude Code already ship CIMD; most other MCP clients are still catching up to the new spec, since it's a recent change.

ClientSupport
Claude CodeSupported — this repository is its connector.
Claude DesktopExpected to work (Anthropic's SDK ships CIMD); not yet independently verified.
Codex CLI, Cursor, VS CodeNot yet — these clients' OAuth flow currently expects DCR, which this spec-forward server doesn't implement. Tracking upstream support; see docs/mcp-contract.json's clientCompatibility field for verification dates and test detail.
WindsurfNot yet, for a different reason — Windsurf's remote MCP support is API-key only as of this writing, and this server has no API-key program at all, OAuth only.

This is an authentication-protocol gap, not a missing feature on Mora's side — CIMD is where the ecosystem is heading, not a workaround. docs/mcp-architecture.md has the full auth-flow diagram and the live test evidence behind the table above.

This isn't a rendering gap other clients will "just work around" — until a client ships CIMD support (or Mora separately stands up a DCR-compatible path, which is not currently planned), the honest answer for an unverified/failing client is "not yet," not "add the URL and see." Machine-readable form of this table: docs/mcp-contract.json's clientCompatibility field. See docs/mcp-architecture.md for the full request/auth flow diagram.

Getting started

Ask the connected agent something like "connect to my Mora account" and the bundled skill walks you through the one-time OAuth consent. Then try:

  • "What already worked before I draft this week's posts?"
  • "Plan my Product Hunt launch week, and follow Product Hunt's current rules."
  • "Name a real product from my catalogue instead of guessing one."

Package targets

Claude Code has the documented turnkey installation path above. The same repository also includes .codex-plugin/plugin.json so Mora AI can be packaged and reviewed as a Codex plugin. That manifest does not change the hosted OAuth flow or upgrade any row in the client-compatibility matrix: the current contract records Codex CLI as not yet supported, Cursor and VS Code as unverified, and Windsurf as blocked by its API-key-only remote MCP path.

Support

License

MIT — see LICENSE.

Source: README.md at commit 56195e9

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.3LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts