Bring Blogging
to CrewAI
Learn how to connect Dev.to (Forem) to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Dev.to (Forem) MCP Server?
Connect your Dev.to or Forem account to any AI agent and manage your technical writing and community presence through natural conversation.
What you can do
- Article Management — List published articles, search by tags, and fetch specific posts by ID or path.
- Content Creation — Create new articles or update existing ones with full markdown support directly from your chat.
- Personal Dashboard — Access your own articles (published or drafts) and retrieve your authenticated user profile using
list_my_articlesandget_me. - Community Insights — Look up other users with
get_user, explore organization-specific content, and list organization members. - Moderation Tools — Unpublish articles when necessary using
unpublish_article(requires appropriate permissions).
How it works
- Subscribe to this server
- Enter your Dev.to/Forem API Key
- Start managing your blog posts and community interactions from Claude, Cursor, or any MCP client
Who is this for?
- Technical Writers — draft and update articles without leaving your markdown editor or IDE.
- Community Managers — monitor organization posts and user profiles efficiently.
- Developers — automate the distribution of technical content and query community data via API.
Built-in capabilities (12)
to/Forem. Requires API key. Create a new article
Get a single article by ID
Get a single article by username and slug
Get authenticated user details
Get a user by ID or username
List published articles
Requires API key. List authenticated user's articles
List organization's articles
List organization's users
List articles with videos
Unpublishes a specific article. Unpublish an article
Requires API key. Update an existing article
Why CrewAI?
When paired with CrewAI, Dev.to (Forem) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Dev.to (Forem) 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
Dev.to (Forem) in CrewAI
Dev.to (Forem) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Dev.to (Forem) 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 | 4,000+ 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 Dev.to (Forem) in CrewAI
The Dev.to (Forem) 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 12 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
Dev.to (Forem) for CrewAI
Every tool call from CrewAI to the Dev.to (Forem) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I publish a new post directly from the chat?
Yes! Use the create_article tool by providing a title and the markdown content. You can also set the published status to true or false for drafts.
How do I see my own drafts and published posts?
You can use the list_my_articles tool. It allows you to filter by type, such as 'all', 'published', or 'unpublished' (drafts).
Can I look up another user's profile information?
Yes, use the get_user tool with either their unique User ID or their username to retrieve their public profile details.
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.
Explore More MCP Servers
View all →
Bevy Community
10 toolsManage your community events and chapters via Bevy — list events, attendees, and chapters directly from any AI agent.
ScraperAPI
10 toolsEquip your AI agent with proxy rotation and headless browsers to extract HTML, Google SERPs, and Amazon data at scale.
Tomorrow.io Alternative
10 toolsAccess hyperlocal weather intelligence — real-time conditions, forecasts, historical archives, severe alerts and route weather from the Tomorrow.io API.
Airparser
10 toolsAI data extraction orchestration — parse PDFs, emails, and images into structured data via AI.