3,400+ MCP servers ready to use
Vinkius

Ghost MCP Server for VS Code CopilotGive VS Code Copilot instant access to 10 tools to Create Post, Get Post Details, Get Site Settings, and more

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Use with Your AI Agent

Ask AI about this App Connector for VS Code Copilot

Open in ChatGPT Open in Claude Open in Perplexity

The Ghost app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 10 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Ghost and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "ghost-alternative": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Ghost
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 publishing account to any AI agent and take full control of your content management and membership workflows through natural conversation.

GitHub Copilot Agent mode brings Ghost data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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

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

All 10 Ghost tools available for VS Code Copilot

When VS Code Copilot connects to Ghost through Vinkius, your AI agent gets direct access to every tool listed below — spanning blogging, newsletter-publishing, membership-sites, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

create_post

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

get_post_details

Essential for reviewing the full content of an article. Get details for a specific post

get_site_settings

Essential for verifying site identity. Get Ghost site settings and configuration

list_members

Includes emails, status, and join dates. List all site members

list_membership_tiers

g., Free, Premium) available on the site. Useful for understanding the subscription structure. List membership tiers and plans

list_newsletters

Newsletters are used to send content updates to members. List all configured newsletters

list_offers

List active membership offers

list_pages

g., About, Contact) defined on the Ghost site. Pages are similar to posts but used for non-blog content. List all static site pages

list_posts

Includes basic metadata and post IDs for detailed retrieval. List all Ghost blog posts

list_tags

Useful for organizing and filtering posts. List all content tags

Connect Ghost to VS Code Copilot via MCP

Follow these steps to wire Ghost into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Create MCP config

Create a .vscode/mcp.json file in your project root
02

Add the server config

Paste the JSON configuration above
03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown
04

Start using Ghost

Ask Copilot: "Using Ghost, help me...". 10 tools available

Why Use VS Code Copilot with the Ghost MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Ghost through the Model Context Protocol.

01

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Ghost + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Ghost MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Example Prompts for Ghost in VS Code Copilot

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

01

"List all my draft posts in Ghost."

02

"Create a new draft titled 'Welcome to our MCP Blog'."

03

"Show me a list of all site members and their emails."

Troubleshooting Ghost MCP Server with VS Code Copilot

Common issues when connecting Ghost to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Ghost + VS Code Copilot FAQ

Common questions about integrating Ghost MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.