Bring Blogging
to CrewAI
Learn how to connect Ghost to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Ghost MCP Server?
Connect your Ghost publishing account to any AI agent and take full control of your content management and membership workflows through natural conversation.
What you can do
- Content Orchestration — List and manage all blog posts (published, draft, scheduled) and retrieve detailed HTML content and metadata programmatically
- Member Intelligence — Query your subscriber directory and retrieve detailed profiles, including join dates and membership tiers to monitor audience growth
- Site Navigation — List and oversee static site pages (About, Contact) and manage content tags to maintain a perfectly organized site taxonomy
- Publishing Control — Create new posts or drafts and update publishing statuses directly through your agent to streamline your editorial pipeline
- Site Visibility — Retrieve general site settings, newsletter configurations, and active membership offers using natural language commands
How it works
1. Subscribe to this server
2. Retrieve your Admin API Key and Admin Domain from Ghost (Settings > Integrations > Custom Integration)
3. Start managing your digital publication from Claude, Cursor, or any MCP client
No more manual dashboard navigation to check post statuses or member counts. Your AI acts as your dedicated content strategist and site manager.
Who is this for?
- Content Managers — instantly retrieve post details and manage drafts without opening the Ghost admin panel
- Digital Publishers — monitor membership tiers and verify newsletter configurations using natural language
- Marketing Teams — automate site settings querying to orchestrate cross-platform content strategies
Built-in capabilities (10)
Requires a title and supports optional HTML content. The post is created as a "draft" by default but can be set to "published" immediately. Create a new Ghost post or draft
Essential for reviewing the full content of an article. Get details for a specific post
Essential for verifying site identity. Get Ghost site settings and configuration
Includes emails, status, and join dates. List all site members
g., Free, Premium) available on the site. Useful for understanding the subscription structure. List membership tiers and plans
Newsletters are used to send content updates to members. List all configured newsletters
List active membership offers
g., About, Contact) defined on the Ghost site. Pages are similar to posts but used for non-blog content. List all static site pages
Includes basic metadata and post IDs for detailed retrieval. List all Ghost blog posts
Useful for organizing and filtering posts. List all content tags
Why CrewAI?
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.
- —
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
mcpsparameter 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 in CrewAI
Ghost and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Ghost to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Ghost in CrewAI
The Ghost 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Ghost for CrewAI
Every tool call from CrewAI to the Ghost MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Ghost Admin API Key?
Log in to your Ghost admin panel, navigate to Settings > Integrations, click Add custom integration, and copy the Admin API Key and API URL.
What is the Admin Domain?
It is the API URL provided in your custom integration settings (e.g., https://your-site.ghost.io). Do not include the /ghost/api/admin/ part.
Can I publish a post immediately via AI?
Yes! When using the create_post tool, set the status parameter to 'published' to make your content live instantly.
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.
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.