Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

Mora AI

de Mora-AI-Content-Studioversión 1.0.3i★ –iSe ejecuta en la nube
Nombre en el registroio.github.Mora-AI-Content-Studio/mora

Instalar

Resumen

Descripción del creador (original en inglés)

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

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en la nube
  • Transporte: Streamable HTTP
  • Categoría: Otros

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

Necesitas

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Funciona en Claude para web, escritorio y móvil:

  1. Abre Settings → Connectors
  2. Presiona Add custom connector
  3. Pega la dirección de abajo y presiona Add
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Add2https://…3
https://app.mora-marketer.com/api/mcp

Ejecuta esto en tu terminal

claude mcp add --transport http mora https://app.mora-marketer.com/api/mcp

Abrir en Cursor

O copia la configuración tú

Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Abrir en VS Code

O copia la configuración tú

Pégalo en .vscode/mcp.json de tu proyecto

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

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

ChatGPT solo se conecta a servidores en internet:

  1. Abre ChatGPT en la web → Settings → Connectors (Apps)
  2. Presiona Create o Add (en algunos planes primero hay que activar Developer mode en Advanced)
  3. Pega la dirección de abajo, ponle un nombre y guarda
  4. Si te pide iniciar sesión, inicia sesión en el servicio del creador
SettingsConnectors1+ Create2https://…3
https://app.mora-marketer.com/api/mcp

Los nombres de los menús pueden variar un poco según el plan y con el tiempo.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Todavía no hemos leído la lista de herramientas de este servidor; revisamos los endpoints por turnos.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub Mora-AI-Content-Studio, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    El endpoint responde

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Inicio de sesión con OAuth

    Aún sin revisar; revisamos los endpoints por turnos

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Aún sin revisar; leemos la lista de herramientas cuando revisamos el endpoint

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 32623 servidores de esta categoría
  • Publicado en el registro más recientemente que el 29% de los otros 32623 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 32623 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Mora AI?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (1.0.3) llegó al registro hace 3 meses.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Draugr

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar

Remote Desktop Commander

de desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Se ejecuta en la nube★ 211Actualizado anteayer
Instalar

Draugr

de draugr-dev

Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.

Se ejecuta en tu computadoraActualizado hoy
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

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:

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

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

Developer documentation:

  • Architecture and data flow
  • Machine-readable contract summary
  • Security policy
  • Contribution guide
  • Changelog and version policy

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

  • Product: https://www.mora-marketer.com
  • MCP server documentation: https://app.mora-marketer.com/developers/mcp
  • Canonical server card: https://app.mora-marketer.com/.well-known/mcp/server-card.json
  • Agent authentication guide: https://www.mora-marketer.com/auth.md
  • Public repository role: this repository is the connector and workflow package; the hosted MCP endpoint is the runtime.
  • Issues with this plugin: open an issue on this repository.

License

MIT — see LICENSE.

Pregunta a PopNx