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.

INSTANT PLUG AND PLAY

BlogIn MCP Server for CrewAIGive CrewAI instant access to 7 tools to Create Internal Post, Get Post Details, List Categories, and more

Name: BlogIn
Availability: InStock
Author: Vinkius

Built by Vinkius GDPR 7 Tools Framework

Connect your CrewAI agents to BlogIn through Vinkius, pass the Edge URL in the `mcps` parameter and every BlogIn tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Use with Your AI Agent

Ask AI about this App Connector for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The BlogIn app connector for CrewAI is a standout in the Collaboration category — giving your AI agent 7 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="BlogIn Specialist",
    goal="Help users interact with BlogIn effectively",
    backstory=(
        "You are an expert at leveraging BlogIn tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in BlogIn "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 7 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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 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.

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.

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.

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

All 7 BlogIn tools available for CrewAI

When CrewAI connects to BlogIn through Vinkius, your AI agent gets direct access to every tool listed below — spanning internal-blog, team-communication, knowledge-sharing, 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_internal_post

Create a new blog post

get_post_details

Get details for a specific post

list_categories

List post categories

list_internal_pages

List internal wiki pages

list_posts

List BlogIn posts

list_recent_comments

List recent post comments

list_team_members

List account users

Connect BlogIn to CrewAI via MCP

Follow these steps to wire BlogIn into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 7 tools from BlogIn

Why Use CrewAI with the BlogIn MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with BlogIn through the Model Context Protocol.

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 `mcps` parameter 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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the BlogIn MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries BlogIn for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries BlogIn, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain BlogIn tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries BlogIn against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for BlogIn in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with BlogIn immediately.

"List the most recent internal blog posts."

"Show me the comments for the post 'Quarterly Roadmap Update'."

"Create an internal post: 'New Benefits Guide' in the 'HR' category."

Troubleshooting BlogIn MCP Server with CrewAI

Common issues when connecting BlogIn to CrewAI through the Vinkius, and how to resolve them.

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.

BlogIn + CrewAI FAQ

Common questions about integrating BlogIn MCP Server with CrewAI.

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.