Content Calendar Agent by Nova (CIVAI) MCP server
co.civai.nova · Updated
I create markdown content calendars and export them as PDFs via PDF Generator MCP
At a glance
Content Calendar Agent by Nova (CIVAI) is an MCP server in the Docs & Knowledge category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 9 tools, including pdf__list_previews, pdf__get_preview and pdf__preview_document. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Content Calendar Agent by Nova (CIVAI) in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Content Calendar Agent by Nova (CIVAI) in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add --transport http content-calendar-agent https://nova.civai.co/mcp/agents/content-calendar-agentVerify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. pdf__list_previews, pdf__get_preview, pdf__preview_document). It discovers them automatically.
How to install Content Calendar Agent by Nova (CIVAI) in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "content-calendar-agent": { "command": "npx", "args": [ "-y", "mcp-remote", "https://nova.civai.co/mcp/agents/content-calendar-agent" ] } } }Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Content Calendar Agent by Nova (CIVAI) in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "content-calendar-agent": { "url": "https://nova.civai.co/mcp/agents/content-calendar-agent" } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Content Calendar Agent by Nova (CIVAI) in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.content-calendar-agent] command = "npx" args = ["-y", "mcp-remote", "https://nova.civai.co/mcp/agents/content-calendar-agent"]Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Content Calendar Agent by Nova (CIVAI) in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "content-calendar-agent": { "serverUrl": "https://nova.civai.co/mcp/agents/content-calendar-agent" } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Content Calendar Agent by Nova (CIVAI) in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "content-calendar-agent": { "type": "streamableHttp", "url": "https://nova.civai.co/mcp/agents/content-calendar-agent" } } }
How to install Content Calendar Agent by Nova (CIVAI) in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "content-calendar-agent": { "type": "http", "url": "https://nova.civai.co/mcp/agents/content-calendar-agent" } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What tools does Content Calendar Agent by Nova (CIVAI) expose? (9)
Read from the live server. Click any tool for its input schema.
- pdf__list_previewsList all stored PDF drafts in this session. Returns previews[{preview_id, title}], count, and most_recent_preview_id. Use when the user taps List PDFs or asks which drafts exist. Does not show document body — follow with get_preview after they pick.
- pdf__get_previewPreview PDF button. Call with no args first: if one draft exists, returns document_markdown; if multiple, returns needs_selection + previews — emit_display layout P (interaction_mode none) numbered picker only. NEVER collect_user_input or emit_display input for preview_id. After user replies with a number/title, call again with preview_id.
- pdf__preview_documentWrite or revise draft markdown into session storage (creates preview_id). Agent-only — not a suggestion button. Use when the user asks to create/write/edit document content. For showing an existing draft use get_preview (Preview PDF). Never put emit_display chrome into content.
- pdf__generate_pdfGenerate a PDF from a preview. Call with no args first: if multiple previews exist, returns needs_selection + previews (title + preview_id) — ask the user which one, then call again with preview_id. If only one preview exists, generates it immediately. Returns pdf_url when generated.
- pdf__delete_previewDelete one stored PDF draft by preview_id from this chat session only. Hidden from suggestion buttons — agent-only. Returns deleted true/false. Does not remove already-generated public PDF files. Never accept path-like ids.
- slide__generate_single_graphic🖼️ Slidegen: generate single graphic
- slide__generate_image🖼️ Slidegen: generate image
- slide__generate_multiple_graphics🖼️ Slidegen: generate multiple graphics
- slide__converseReply conversationally when the request is ambiguous or needs clarification.
What the code can do
This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Third-party hosted service — Your requests and any data in them are sent to nova.civai.co.
- No local execution — Nothing is installed or run on your machine.
- No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.
Client compatibility
Health score
D · 33Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%not measurable
No commit history available.
- Adoption20%not measurable
No usage data available.
- Transparency20%25%
1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.
- Provenance15%0%
No source repository to trace the code back to.
- Packaging15%75%
Remote endpoint; authentication requirements not declared.
Alternatives to Content Calendar Agent by Nova (CIVAI)
- Timothe's Growth CalendarB · 65Plan, schedule and generate SEO articles on a content calendar, from your agent.
- Agent-Native CalendarA · 88Agent-Native Google Calendar - manage events, sync, and public booking
- Calendar Agent by Nova (CIVAI)D · 33I do everything related to calendar scheduling
- Agent GuildB · 79See and steer Claude Code, Codex, Antigravity, Grok, Docker Agent and shell sessions in Agent Guild.
Maintain Content Calendar Agent by Nova (CIVAI)? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/co-civai-nova-content-calendar-agent)Catalog data refreshed . Something wrong? Report it.