How do I get a Content API Key for Ghost?

Log in to your Ghost Admin dashboard, navigate to Settings > Integrations, and add a Custom Integration. You will find the Content API Key there.

Can I publish new posts using this integration?

No, this integration uses the Content API which is read-only. It is designed to safely retrieve and query your published content.

What is the Base URL format?

Your Base URL is the root domain where your Ghost site is hosted, for example: 'https://demo.ghost.io'. Do not include '/ghost/api/'.

How do I fetch related tags and authors for a post?

Use the 'include' parameter in the 'get_post_by_slug' tool and pass the string 'tags,authors'.

Ghost MCP Server for CrewAI 11 tools — connect in under 2 minutes

Name: Ghost
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 11 Tools Framework

Connect your CrewAI agents to Ghost through Vinkius, pass the Edge URL in the `mcps` parameter and every Ghost tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Ghost Specialist",
    goal="Help users interact with Ghost effectively",
    backstory=(
        "You are an expert at leveraging Ghost tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Ghost "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 11 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Ghost MCP Server

Connect your Ghost publication to any AI agent to automate your content management workflows through the Model Context Protocol (MCP). Ghost is a powerful headless Node.js CMS tailored for modern publishing. This MCP server enables you to retrieve published posts, manage taxonomy tags, and fetch site configurations directly through natural conversation using the Ghost Content API.

When paired with CrewAI, Ghost becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Ghost tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

Key Features

Content Discovery — List all published blog posts and static pages, retrieving detailed HTML content and metadata.
Taxonomy Oversight — Retrieve and list all categorization tags to understand your content architecture.
Author Management — Fetch profile details for active writers and contributors across the publication.
Site Configuration — Access global settings, routing rules, and title schemas programmatically.
Subscription Insights — Retrieve active membership tiers to understand paywall rules and pricing layers.
Real-time Synchronization — Keep your headless CMS content accessible to your AI assistant without leaving your primary workspace.

The Ghost MCP Server exposes 11 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Ghost to CrewAI via MCP

Follow these steps to integrate the Ghost MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 11 tools from Ghost

Why Use CrewAI with the Ghost MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Ghost through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Ghost + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Ghost MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Ghost for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Ghost, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Ghost tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Ghost against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Ghost MCP Tools for CrewAI (11)

These 11 tools become available when you connect Ghost to CrewAI via MCP:

get_author_details

Get author profile

get_page_by_slug

Get page details

get_post_by_slug

Get post details

get_site_settings

Get site settings

get_tag_details

Get tag metadata

list_blog_authors

List authors

list_content_tags

List categories/tags

list_published_posts

List published posts

list_static_pages

List static pages

list_subscription_tiers

List subscription tiers

verify_api_connection

Check connection

Example Prompts for Ghost in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Ghost immediately.

"List the 5 most recent published posts."

"Get the content of the post with the slug 'welcome'."

"List all active subscription tiers."

Troubleshooting Ghost MCP Server with CrewAI

Common issues when connecting Ghost to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Ghost + CrewAI FAQ

Common questions about integrating Ghost MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.