Data & contentPublic source

Content Management MCP Server

Unified content platform for AI agents — manage articles, social media, YouTube videos, media library, SEO, and publishing workflows from a single MCP server. 26 tools across content, social, and video.

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Provides cms capabilities through a typed MCP contract.

Architecture

How Content Management MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Content Management MCP Server

Validates the request and owns 26 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Content Management MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Content Management MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

26 named tools

list_content

List articles/pages by status, type, channel

see documentation

get_content

Full content with metadata + SEO

see documentation

create_content

Create article/page (draft)

see documentation

update_content

Update body, title, tags

see documentation

publish_content

Publish to website (goes live)

see documentation

unpublish_content

Take offline

see documentation

list_social_accounts

Connected accounts (Twitter, LinkedIn, IG, FB)

see documentation

schedule_social_post

Schedule post to platforms

see documentation

get_social_metrics

Engagement: likes, shares, reach

see documentation

list_scheduled_posts

Upcoming scheduled posts

see documentation

delete_scheduled_post

Cancel a scheduled post

see documentation

list_videos

List videos

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

26 see documentation

Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-cms

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-cms",
    ["mcp-cms"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Api Reference ↗docs/api-reference.md Overview ↗example-backend/README.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring