Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Codex guesses your brand voice. Mora AI gives it the real one: your catalogue and performance.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://app.mora-marketer.com/api/mcpRun this in your terminal
claude mcp add --transport http mora https://app.mora-marketer.com/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mora": {
"url": "https://app.mora-marketer.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"mora": {
"type": "http",
"url": "https://app.mora-marketer.com/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://app.mora-marketer.com/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account Mora-AI-Content-Studio, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, 御府和田玉 在售作品查询
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Live in-stock Hetian jade from Yufu, Shanghai: prices, monthly price guide, book a viewing.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Codex guesses your brand voice. Mora AI gives it the real one, plus your real catalogue and performance.
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.
.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.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.mora://brand/voice) you can attach once per session so every message Claude writes stays on-brand, without re-fetching it per message.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.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.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.
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:
node scripts/check-mora-mcp-contract.mjs
For an offline fixture, set MORA_MCP_SERVER_CARD_FILE=/path/to/server-card.json.
Developer documentation:
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.
| Client | Support |
|---|---|
| Claude Code | Supported — this repository is its connector. |
| Claude Desktop | Expected to work (Anthropic's SDK ships CIMD); not yet independently verified. |
| Codex CLI, Cursor, VS Code | Not 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. |
| Windsurf | Not 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.
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:
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.
MIT — see LICENSE.