mcpField
E
EM+x

EM+x

VerifiedFeaturedRemote
emplusx.comProductivity0Updated 10w ago

About EM+x

EM+x is a remote MCP server that turns conversation briefs into branded PPTX and DOCX deliverables. It guides teams through structure approval, multi-agent review, revisions, and previews for management-facing documents.

Key features

  1. 01Generate PPTX and DOCX from briefs
  2. 02Approve document structure page by page
  3. 03Run multi-agent quality reviews
  4. 04Revise by prompt and manage versions
  5. 05Preview, approve, and download files
  6. 06Manage brand templates and styles

Use cases

  1. 01Prepare steering-committee readouts
  2. 02Write executive briefs and program updates
  3. 03Create QBR presentations
  4. 04Apply organizational templates to deliverables

MCP support

EM+x exposes tools for creating, generating, refining, previewing, approving, and downloading deliverables to MCP clients over Streamable HTTP. Connections use OAuth 2.1.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://emplusx.com/api/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

33
ParameterTypeRequiredDescription
briefobjectYes
brief.titlestringYesDeliverable title
brief.audiencestringYesWho consumes this, e.g. 'exec steering committee'
brief.decisionstringYesThe decision or action the deliverable must drive
brief.deliverable_typeenumNomemo | report | deck | one-pager
brief.consumptionenumNo'cold' = read unaccompanied; 'accompanied' = presented livecold | accompanied
brief.domainstringNo
brief.recipient_realitystringNoWhat the recipients already believe/know, constraints, politics
brief.rosterarrayNo
brief.instructionsstringNoAny additional shaping guidance from the user
brief.max_pagesanyNoHard page budget INCLUDING the cover (a deck gets one page per section plus the cover). Set it from the user's stated number; if they haven't given one, ASK for a maximum page count - or omit the field when they say to let the engine decide. Never translate vague size words like 'short' into a guess without asking.
brief.evidencearrayNoSource material: notes, data extracts, prior docs, transcripts
formatsarrayYesOutput formats to build
idempotency_keystringYes
templatestringNoName (or id) of a brand template from the user's library - see list_templates. Applied as a copy at creation. Omit for the EM+x default style.

Details

From the project README

EM+X — MCP server

Finished, on-brand .pptx and .docx from a brief — quality-gated by an agentic consulting team.

EM+X is a remote MCP server. Connect it to any MCP-capable client (Claude, ChatGPT, Cursor, Codex, Grok, Copilot, …) and your assistant can assemble a brief from the conversation, propose a document structure for your approval, generate a presentation or document through a multi-agent quality-gate stack, refine it by prompt, preview pages in an interactive panel, and hand you a download link for the finished file.

  • Claude directory listing: https://claude.ai/directory/em-x
  • Connector URL: https://emplusx.com/api/mcp
  • Transport: streamable HTTP
  • Auth: OAuth 2.1 with dynamic client registration — sign in with your EM+X account; no API keys, no parameters to configure
  • Pricing: works on every plan, including the free tier (pricing)
  • Docs: https://emplusx.com/mcp

This repository is a thin, MIT-licensed descriptor for the hosted service — the connector metadata and install instructions live here; the service itself runs at emplusx.com.

Install

Claude (web / desktop / mobile)

EM+X is a listed connector in the Claude directory: open claude.ai/directory/em-x and click Connect — no URL to paste, and one connect covers claude.ai, Claude Desktop, and mobile. In the desktop app, claude://claude.ai/directory/em-x opens the listing directly. (Step-by-step: https://emplusx.com/connect)

Claude Code
claude mcp add --transport http emplusx https://emplusx.com/api/mcp
Cursor

Install in Cursor — or add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "emplusx": {
      "url": "https://emplusx.com/api/mcp"
    }
  }
}
Any other MCP client

Point the client at https://emplusx.com/api/mcp (streamable HTTP). The OAuth flow is discovered automatically per RFC 9728; the browser opens the EM+X sign-in and you're connected.

What the tools do

The server exposes 33 tools. The core flow:

ToolWhat it does
create_deliverableFiles a brief (title, audience, decision, evidence) and proposes a page-by-page structure
update_briefEnriches the brief and re-proposes — the server flags thin evidence rather than guessing
confirm_and_generateBuilds the document through the quality-gate stack (architect, writer, designer, critic, partner review)
refine_deliverableRevises a built document by instruction ("tighten section 2") — every revision is a new version
approve_deliverableRecords sign-off on the exact version reviewed
get_download_linkMints an expiring link for the finished .pptx / .docx
list_templates / get_template_upload_linkManage the brand-template library from chat
clone_styleReuses another project's extracted brand style
show_deliverable_panelOpens an interactive panel (MCP Apps): outline review, live build progress, page previews, version compare, refine/approve/download

The remaining tools power the interactive panel (page previews, version scrubbing, account/usage display) on hosts that support MCP Apps; on text-only hosts the flow works through the core tools alone.

Links

License

The contents of this repository (metadata and documentation) are MIT-licensed. The EM+X service is a commercial product of Cubed Studios, a subsidiary of Cubed Ventures LLC.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.