Skip to main content
Glama

Manic MCP Server

Give any MCP-capable AI — Claude Code, Claude Desktop, or a local model — the ability to write, validate, and render Manic animations.

The connected model is the author: this server deliberately has no AI- generation tool and spends no Manic AI credits. Instead it hands the model the complete Manic authoring guide, then lets it validate its own .manic source and render real videos through the Manic platform with your API key.

Tools

Tool

Auth

What it does

manic_authoring_guide

none

Fetches the full, current Manic language guide — the same system prompt Manic's own AI uses. The model reads this once, then writes real Manic.

manic_check

API key (check)

Validates .manic source and returns exact diagnostics. Cheap — always check before rendering.

manic_render

API key (render:create)

Submits source to the hosted renderer (mp4/gif/webm/mov/still). Returns a durable job id. Spends export credits.

manic_render_status

API key (jobs:read)

Polls a render job; returns the artifact URL when done, or the exact compile error to fix.

manic_save_to_project

API key (projects:read/write)

Saves the file into your Manic project, where it opens in Manic Create and Manic Workbench.

The intended loop: guide → write → check → (fix → check…) → render → poll → video — with every generated file optionally saved as a real project document.

Related MCP server: Cognitive Core

Setup

Create an API key at app.maniclang.com/account with scopes: check, render:create, jobs:read, projects:read, projects:write. (Without a key, only manic_authoring_guide works.)

No install needed — npx runs the published package directly.

Claude Code

claude mcp add manic -e MANIC_API_KEY=mk_live_… -- npx -y @maniclang/mcp-server

Claude Desktop / other MCP clients

{
  "mcpServers": {
    "manic": {
      "command": "npx",
      "args": ["-y", "@maniclang/mcp-server"],
      "env": { "MANIC_API_KEY": "mk_live_…" }
    }
  }
}

From source (development)

npm install && npm run build

Then use node /path/to/manic-mcp-server/dist/index.js as the command instead of npx -y @maniclang/mcp-server in any config above.

Other clients

Cursor, Windsurf, Cline, Continue, Zed, LM Studio, and any generic stdio MCP client — see docs/USAGE.md for copy-paste configs, the intended authoring loop, example prompts, the cost model, and troubleshooting.

Configuration

Variable

Default

Purpose

MANIC_API_KEY

Your Manic API key; required for everything except the authoring guide

MANIC_API_BASE_URL

https://api.maniclang.com/v1

Platform API base

MANIC_SYSTEM_PROMPT_URL

the hosted Manic guide

Override the authoring-guide source

Try it

Ask your model:

"Read the Manic authoring guide, then create a 15-second animation of a pendulum tracing its path, validate it, render it as mp4, and give me the video link."

Install Server
A
license - permissive license
A
quality
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

View all related MCP servers

Related MCP Connectors

  • Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.

  • Generate on-brand images from your AI agent: design, edit, and render templates over MCP.

  • Hosted email MCP for AI agents with inboxes, send/receive, memory, recovery, and credits.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/maniclang-x/-manic-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server