Bring Internal Blog
to VS Code Copilot
Learn how to connect BlogIn to VS Code Copilot and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the BlogIn MCP Server?
Connect your BlogIn internal blog to any AI agent and simplify how you share knowledge, track team updates, and manage your company's internal wiki through natural conversation.
What you can do
- Post Management — List all internal blog posts and retrieve detailed metadata and HTML content for specific entries.
- Content Creation — Programmatically create new blog posts with titles, categories, and full text directly via AI.
- Wiki & Pages — Query static internal pages to access company policies, handbooks, and static documentation.
- Team Directory — List account users and members to understand your organizational structure and contributors.
- Discussion Tracking — Monitor recent comments across all posts to stay on top of internal feedback.
- Categorization — List and browse post categories to find relevant content by topic.
How it works
1. Subscribe to this server
2. Enter your BlogIn API Key and Subdomain (found in your account settings)
3. Start managing your internal knowledge base from Claude, Cursor, or any MCP client
Who is this for?
- Internal Communicators — quickly retrieve recent updates and publish new announcements via simple AI commands.
- HR & Operations — verify company policies and manage internal wiki pages directly from the workspace.
- Team Leads — monitor discussion comments and retrieve contributor profiles via the AI assistant.
Built-in capabilities (7)
Create a new blog post
Get details for a specific post
List post categories
List internal wiki pages
List BlogIn posts
List recent post comments
List account users
Why VS Code Copilot?
GitHub Copilot Agent mode brings BlogIn data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
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
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
BlogIn in VS Code Copilot
BlogIn and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BlogIn to VS Code Copilot 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 BlogIn in VS Code Copilot
The BlogIn 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 7 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot 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
BlogIn for VS Code Copilot
Every tool call from VS Code Copilot to the BlogIn MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see the HTML content of a specific internal post via AI?
Yes! Use the get_post_details tool and provide the Post ID. Your agent will retrieve the complete metadata and HTML body for that specific blog entry.
How do I list all the static wiki pages in my account?
Run the list_internal_pages query. The agent will retrieve a complete list of all static, wiki-style pages currently configured in your BlogIn account.
Is it possible to create a new internal post via AI?
Absolutely. Use the create_internal_post action. Provide a title, the content, and an optional category ID to publish a new update instantly to your team.
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.
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.
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.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.