Bring Internal Blog
to CrewAI
Learn how to connect BlogIn to CrewAI 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 CrewAI?
When paired with CrewAI, BlogIn becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call BlogIn 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
BlogIn in CrewAI
BlogIn and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect BlogIn 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 BlogIn in CrewAI
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 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
BlogIn for CrewAI
Every tool call from CrewAI 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 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.