Write in Your IDE.
Publish Everywhere.

Connect Claude Code, Cursor, Windsurf, or VS Code to ZyVOP's hosted MCP server. Draft, schedule, and syndicate across connected networks without leaving your editor.

Get Developer TokenMCP Protocol Specs

Compatible with standard MCP clients:

Claude CodeCursorWindsurfVS Code (Cline / Roo)OpenAI CodexKiro

Configure Your AI Assistant

Select your AI coding tool. Paste your developer token to customize your configuration snippet.

Inject Your Developer Token

Optional: paste your token to auto-populate the snippet below.

Generate Token

Official CLI Command & .mcp.json

Claude Code Configuration

Add ZyVOP directly to Claude Code via terminal CLI or configuration file to publish articles and review analytics inside your conversational coding session.

~/.claude.json or project .mcp.json

CLI Quickstart Command

claude mcp add --transport http zyvop https://zyvop.com/mcp \
  --header "Authorization: Bearer <YOUR_ZYVOP_TOKEN>"

Configuration File (~/.claude.json or project .mcp.json)

{
  "mcpServers": {
    "zyvop": {
      "type": "http",
      "url": "https://zyvop.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_ZYVOP_TOKEN>"
      }
    }
  }
}

Setup Instructions

1Generate a developer token in Settings → Integrations.
2Run the one-line `claude mcp add` command in your terminal.
3Ask Claude: "Publish my latest README notes as a draft on ZyVOP and DEV.to."

Keep your token safe: Always use personal, user-level settings (like ~/.claude.json or your personal IDE settings) rather than committing secret tokens into shared project repositories.

Available MCP Tools

Five JSON-RPC tools with structured inputs, strict typing, and retry-safe idempotency controls.

Available Tools (5)

zyvop_create_post

Create, schedule, or publish a post

MutationPublishing

Create a technical Markdown article as a draft, schedule it for a future timestamp, or publish immediately with automated multi-network syndication.

Arguments Schema (8 parameters)

Parameter	Type	Description
title*	string (3-200 chars)	Post headline.
markdown*	string	Complete article body in Markdown with code blocks and KaTeX/Mermaid.
publish_mode	'draft' \| 'schedule' \| 'publish'	Target lifecycle state (defaults to draft).
scheduled_at	ISO 8601 string	Future ISO timestamp required when publish_mode is 'schedule'.
excerpt	string (max 500 chars)	Short summary for SEO meta descriptions and social cards.
cover_image	URI string	URL to article hero image.
tags	string[] (max 10)	Relevant topic tags.
cross_post_to	string[]	Connected channels: devto, hashnode, medium, wordpress, bluesky, mastodon, linkedin.

Sample JSON-RPC Tool Call

{
  "name": "zyvop_create_post",
  "arguments": {
    "title": "Optimizing Node.js Stream Pipelines",
    "markdown": "# Stream Pipelines\n\nIn this guide, we benchmark high-throughput backpressure...",
    "publish_mode": "publish",
    "tags": ["nodejs", "backend", "performance"],
    "cross_post_to": ["devto", "hashnode", "linkedin"]
  }
}

Example Agent Prompts

Copy these real-world prompts into Claude Code or Cursor to publish, syndicate, and inspect performance directly from your terminal.

agent-conversation · Publish & Syndicate

Developer Prompt

Turn my local docs/architecture.md into a high-quality blog post. Publish to ZyVOP, cross-post to DEV.to, and share a summary on LinkedIn.

Agent Reasoning

I will first read the local architecture.md, format it into clear Markdown with frontmatter, verify connected channels via zyvop_get_connected_platforms, and call zyvop_create_post with cross_post_to: ["devto", "linkedin"].

Executed MCP Tool Invocations

→zyvop_get_connected_platforms()

→

zyvop_create_post(title: "Inside Our Distributed Cache Architecture", publish_mode: "publish", cross_post_to: ["devto", "linkedin"])

Assistant Response

✅ Article published successfully! - **ZyVOP Canonical**: https://zyvop.com/@author/inside-our-distributed-cache-architecture - **DEV.to Syndication**: Dispatched with rel="canonical" configured - **LinkedIn Announcement**: Scheduled dispatch triggered Your post is live and indexing with machine-readable JSON-LD metadata.

Security & Execution Architecture

Built for coding-agent workflows with defensive defaults, request-level observability, and revocable user tokens.

Hosted Remote Architecture

Zero local daemons or background Node.js servers to keep running. Your agent interacts directly with ZyVOP’s secure cloud JSON-RPC endpoint over HTTPS.

Hashed Scoped Tokens

Developer tokens are prefixed with `zv_` and securely hashed using cryptographic standards. Instantly rotate or revoke compromised tokens.

Safe Draft Defaults

The publishing tool defaults to `publish_mode: draft`. Runaway or exploring agents cannot accidentally broadcast live content without explicit confirmation.

Runaway Agent Protection

Backend rate limiting guards prevent accidental recursive agent loops from consuming resources or flooding connected syndication platforms.

Idempotent Upsert Logic

Posts match existing slugs, canonical URLs, or identifiers so agent network retries update existing records rather than create duplicate articles.

Standard MCP Versioning

Full support for standard protocol specifications (2025-11-25, 2025-06-18, 2025-03-26, and 2024-11-05) with automatic server capability negotiation.

Frequently Asked Questions

Everything you need to know about protocol support, security tokens, agent permissions, and syndication on ZyVOP.

The Model Context Protocol (MCP) is an open standard introduced by Anthropic that allows AI applications (such as Claude Code, Cursor, Windsurf, and VS Code) to securely interact with external tools and data sources. ZyVOP provides a hosted MCP server over HTTP JSON-RPC, meaning you can publish and manage technical articles without installing local bridge daemons.

No. ZyVOP hosts the MCP endpoint remotely at `https://zyvop.com/mcp`. You simply add the HTTP URL and your developer token to your client’s configuration (e.g. `claude mcp add --transport http` or `.cursor/mcp.json`). There are zero local background processes to keep alive.

Log into ZyVOP, navigate to **Settings → Integrations**, and locate the **ZyVOP API, CLI & MCP** panel. Click "Generate Token" to create a personal Bearer token prefixed with `zv_`. This token works across the CLI, REST API, and MCP server.

You are in full control. By default, ZyVOP’s `zyvop_create_post` tool defaults to `publish_mode: "draft"`. AI clients with confirmation prompts (like Claude Code or Cursor) will display the tool call arguments and ask for your approval before calling destructive tools. You can also specify in your agent prompt to only create drafts.

Any platform connected in your ZyVOP Integrations settings can be selected: DEV.to, Hashnode, Medium, WordPress, Bluesky, Mastodon, and LinkedIn. Your agent can call `zyvop_get_connected_platforms` to see what is currently configured before initiating syndication.

ZyVOP supports the official Model Context Protocol specifications including versions `2025-11-25`, `2025-06-18`, `2025-03-26`, and `2024-11-05` with automatic protocol negotiation.

Yes. In **Settings → Integrations**, you can regenerate or revoke your developer token instantly. Any MCP servers, CLI terminals, or CI/CD pipelines using the old token will immediately lose access.

Publish directly from your AI coding assistant.

Generate a developer token in seconds. Add ZyVOP to Claude Code, Cursor, Windsurf, or VS Code and publish directly from your terminal.

Generate Developer Token Read Full API & CLI Docs

Standard MCP 2025-11-25 Compliant · Zero Local Node Process · Free for All Authors

Zero Local Overhead

Connect via remote HTTPS. No background processes, no memory leaks, and no daemon crashes on your laptop.

Defensive Defaults

Publishing calls draft by default. Every action is authenticated, hashed, and scoped to your author account.

Omnichannel Reach

Syndicate to DEV.to, Hashnode, Medium, and WordPress, and announce to LinkedIn, Bluesky, and Mastodon.

Write in Your IDE. Publish Everywhere.