Bring Internal Blog
to Claude Code
Learn how to connect BlogIn to Claude Code 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 Claude Code?
Claude Code registers BlogIn as an MCP server in a single terminal command. Once connected, Claude Code discovers all 7 tools at runtime and can call them headlessly. ideal for CI/CD pipelines, cron jobs, and automated workflows where BlogIn data drives decisions without human intervention.
- —
Single-command setup:
claude mcp addregisters the server instantly. no config files to edit or applications to restart - —
Terminal-native workflow means MCP tools integrate seamlessly into shell scripts, CI/CD pipelines, and automated DevOps tasks
- —
Claude Code runs headlessly, enabling unattended batch processing using BlogIn tools in cron jobs or deployment scripts
- —
Built by the same team that created the MCP protocol, ensuring first-class compatibility and the fastest adoption of new protocol features
BlogIn in Claude Code
BlogIn and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BlogIn to Claude Code 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 Claude Code
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 Claude Code 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 Claude Code
Every tool call from Claude Code 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.
How do I add an MCP server to Claude Code?
Run claude mcp add --transport http "" in your terminal. Claude Code registers the server and discovers all tools immediately.
Can Claude Code run MCP tools in headless mode?
Yes. Claude Code supports non-interactive execution, making it ideal for scripts, cron jobs, and CI/CD pipelines that need MCP tool access.
How do I list all connected MCP servers?
Run claude mcp in your terminal to see all registered servers and their status, or type /mcp inside an active Claude Code session.
Command not found: claude
Ensure Claude Code is installed globally: npm install -g @anthropic-ai/claude-code
Connection timeout
Check your internet connection and verify the Edge URL is reachable