Your agent calls ngram like any other tool.
ngram exposes a native Model Context Protocol server. Claude Desktop, Cursor, Cline, ChatGPT Connectors and any custom MCP client can render videos, fetch status, list past renders and read credit balances inside the same chat - no UI, no copy-paste.
- Native MCP server — every ngram endpoint exposed as a discrete tool with an agent-friendly JSON schema
- stdio and HTTP transport — local stdio for desktop clients, hosted HTTPS endpoint at mcp.ngram.com for remote agents
- Bearer-key auth — one ngs_ key carries the same permissions as your dashboard - validated per request, never logged
Four steps from MCP config to a rendered video in chat.
ngram speaks the open MCP spec end to end. Drop your bearer key into the client config, restart, and ask the assistant for a video. No SDK, no glue code.
Create an ngram API key
Open Settings then API Keys in your ngram dashboard. Keys start with ngs_ and inherit your account permissions. Revoke or rotate any time.
20 secPoint your MCP client at ngram
Edit the client config - Claude Desktop, Cursor, Cline, Notion AI, ChatGPT Connectors. Add ngram as a server via the npm package for stdio or the hosted URL for HTTP.
1 minAsk the assistant for a video
Open chat and describe the video. The agent picks the right tool from the exposed schema - create, status, list, credits - and fires the call directly against ngram.
however long you talkGet a publish-ready MP4 in the thread
Render runs server-side, status streams back as tool output, the final MP4 URL drops into the same chat. Hand off to the editor or post downstream.
~45 secEvery ngram endpoint, mapped to an agent-friendly tool call.
Works in every MCP-aware client
Claude Desktop, Cursor, Cline, Notion AI and ChatGPT Connectors connect with a single config block. Anything that speaks MCP 1.0 just works.
Bearer-key auth, validated per request
One ngs_ key on every call. Validated against the same auth layer as the dashboard, scrubbed from logs, revokable from Settings.
Tool surface mirrors the public API
create_video, get_status, list_videos, get_credits, cancel_render - each ngram endpoint maps to a discrete MCP tool with typed inputs and outputs.
Streaming tool output for long renders
Renders take 30-90 seconds. Status streams back to the client so the agent sees progress, not a frozen tool call.
Every call observable in PostHog
Path, method, user agent, duration, status - every tool invocation flows through PostHog with an anonymized distinctId for end-to-end observability.
Hosted or self-run
Point at the managed mcp.ngram.com endpoint, or run the official @ngramdata/mcp-server npm package locally for stdio clients - same protocol, same schema.
Three agent workflows that collapse into a single tool call.
Agent-driven render in a longer workflow.
An agent researches a topic, drafts the script, fires create_video, polls get_status, then hands the MP4 to the next step. The render is just a tool call inside a longer chain.
See the explainer playbookDev assistants that ship release videos.
Wire ngram into Cursor or your internal IDE assistant. The same chat that writes the changelog also renders the demo video that ships with it.
See the changelog playbookKnowledge bases that produce videos on demand.
Pair Notion AI or an internal RAG agent with ngram. When a customer asks a question, the agent answers in text and renders a 45-second video walkthrough in the same response.
See the help center playbookFive clients we test against. Plus the open MCP spec.
If a client implements MCP 1.0, ngram connects. The clients below are what our team uses day-to-day - the rest of the ecosystem inherits the same protocol.
What runs when the agent fires the render tool.
Every MCP tool call routes into the same ngram pipeline that powers every other integration. Here is what happens inside it.
AI Visuals
Scene-matched graphics in 30+ styles, generated from the prompt the agent passed in.
Explore featureAI Voiceover
40+ voices in 20 languages, auto-synced to the generated timeline.
See featureScript Generation
Scripts written from the agent prompt or any source URL the tool call references.
See featureMusic
Licensed tracks, auto-ducked under the voiceover the agent requested.
See featureMotion Graphics
Auto-animated text, transitions and charts. Zero timeline work for the agent.
See featureCaptions
Burned-in or .srt captions, frame-accurate and editable by humans after the agent hands off.
See featureBrand Kit
The same brand kit applies regardless of trigger - the agent gets the same output a human would.
See featureMulti-format Export
Tool call picks the aspect ratio. 16:9, 9:16, 1:1, 4:5 up to 4K.
See featureEnterprise Integrations
The MCP server is one of many triggers - Zapier, n8n, Make and the Chrome extension share the same backend.
See featureEvery tool call is a converter invocation.
Agents call ngram with a source - URL, text, doc, file. The MCP server routes the call to the right converter based on input type, so the agent never has to pick.
URL to Video
Agents that browse the web hand off URLs to the converter. The render call returns an MP4 URL back into the conversation.
Convert from URLText to Video
When the agent has already written a script or summary, the text converter renders it directly without a source page.
Convert textDocs to Video
Agent context often includes a doc. Route it to the docs converter for a structure-aware video walkthrough.
Convert docsWhat an agent can call after the first render.
Every ngram tool is reachable from the MCP server. Polish, translate or re-cut the output without leaving the agent loop.
Who reaches for the MCP server first.
Developers building agent-augmented products. Ops teams running agentic workflows. AI-native teams who live in chat clients all day.
Wire ngram into the same MCP client your team uses to ship code. Release demos and API walkthroughs render from the same chat.
An MCP-aware agent watches release notes and renders a changelog video the moment the PR merges - no human in the loop.
One AI assistant, every artifact. Investor updates, blog posts and explainer videos all get rendered from the same chat thread.
An internal agent reads the ticket, drafts the answer, and renders a 60-second walkthrough as a single MCP tool call attached to the reply.
Reps stay in their assistant. The agent fires a render against the help center article, posts the video into the ticket, and moves on.
An agent monitors release notes and renders a launch video the same hour the PRD ships - no humans needed for the first cut.
The MCP server is one trigger. Here are the others.
Same rendering engine behind every integration. Pick the trigger that matches the agent or workflow you already run.
Chrome ExtensioncreatePin ngram to your Chrome toolbar. The human-facing trigger - one click on any page returns a publish-ready video.
Explore Chrome Extension integration
ZapiercreateWire ngram into 6,000+ apps. When a CRM event fires, render a personalized clip - no agent reasoning required.
Explore Zapier integration
Make.comcreateVisual scenario builder. Use it for branching workflows with loops, filters and error paths around every render call.
Explore Make.com integration
n8ncreateSelf-hosted workflows. The render API is the only thing leaving your infrastructure - everything else stays in your container.
Explore n8n integration
LinkedInpublishSchedule the agent-rendered video straight to a company or personal LinkedIn page from inside the ngram editor.
Explore LinkedIn integration
X (Twitter)publishPost agent-rendered videos to X with copy, captions and platform-ready aspect ratios attached.
Explore X (Twitter) integration
YouTubepublishUpload with title, description, chapters and tags pre-filled from the prompt that triggered the render.
Explore YouTube integrationWhen MCP is the right trigger, and when it isn't.
ngram MCP you are here | REST API raw HTTP | HTTP webhook event hook | Zapier automation | |
|---|---|---|---|---|
| Who triggers it | An AI agent in chat | Your application code | An upstream event in another system | An automated multi-step Zap |
| Setup time | About 2 minutes - one config block | About 1 hour engineering | About 15 minutes per endpoint | About 5 minutes per Zap |
| Auth model | Bearer ngs_ key per request | Bearer ngs_ key per request | Signed HMAC payload | Stored OAuth or API key |
| Schema for the caller | Agent-friendly JSON schema per tool | Raw OpenAPI spec | Single payload contract | Action form fields in the Zap editor |
| Streaming status | Yes, tool output streams progress | Yes, via polling or SSE | No, fire-and-forget | No, polled by Zapier |
| Best for | Chat-driven agents and copilots | Embedding ngram inside your product | Reacting to upstream system events | No-code multi-step pipelines |
FAQ
Common questions about the MCP server
Still curious? Still curious? Chat with us
Point your agent at ngram. Render in chat.
One config block, one bearer key, every ngram endpoint exposed as a tool call your assistant already knows how to use.