How do I get a Craftnet API Key?

Log in to your Craft ID account at craftcms.com, go to **Settings > API Keys**, and generate a new key. Note that some endpoints require developer permissions.

Can I manage client licenses via chat?

Yes, you can list all CMS and plugin licenses associated with your account, helping you audit and track renewals or project-specific assignments.

Does the integration track plugin sales?

Yes, if you are a plugin developer, you can list your recent sales history and historical payout data directly through the agent.

Craft CMS (Craftnet) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Craft CMS (Craftnet)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Craft CMS (Craftnet) Specialist",
    goal="Help users interact with Craft CMS (Craftnet) effectively",
    backstory=(
        "You are an expert at leveraging Craft CMS (Craftnet) 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 Craft CMS (Craftnet) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Craft CMS (Craftnet) MCP Server

Integrate Craftnet, the developer services platform for Craft CMS, directly into your AI workflow. Manage your published plugins, audit CMS and plugin licenses, and track your developer sales using natural language.

When paired with CrewAI, Craft CMS (Craftnet) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Craft CMS (Craftnet) 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

Plugin Management — List and retrieve details for all plugins published on the Craft Store.
License Auditing — Monitor Craft CMS and plugin licenses associated with your account.
Sales & Payouts — Track recent sales transactions and historical payout data for your developer profile.
Account Insights — Access metadata for your Craftnet account and explore plugin categories.

The Craft CMS (Craftnet) MCP Server exposes 10 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.

How to Connect Craft CMS (Craftnet) to CrewAI via MCP

Follow these steps to integrate the Craft CMS (Craftnet) MCP Server with CrewAI.

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 10 tools from Craft CMS (Craftnet)

Why Use CrewAI with the Craft CMS (Craftnet) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Craft CMS (Craftnet) 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

Craft CMS (Craftnet) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Craft CMS (Craftnet) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Craft CMS (Craftnet) 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 Craft CMS (Craftnet), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Craft CMS (Craftnet) 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 Craft CMS (Craftnet) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Craft CMS (Craftnet) MCP Tools for CrewAI (10)

These 10 tools become available when you connect Craft CMS (Craftnet) to CrewAI via MCP:

get_account_details

Retrieve metadata for your Craftnet account

get_plugin_details

Get detailed information for a specific plugin

list_cms_licenses

List all Craft CMS licenses in your account

list_craftnet_users

List users associated with your Craftnet account

list_payout_history

List historical payouts for plugin developers

list_plugin_categories

List all plugin categories on the Craft Store

list_plugin_licenses

List all plugin licenses purchased or managed

list_plugins

List all plugins published on Craftnet

list_sales_history

List recent sales transactions

search_plugins_by_name

Search for plugins by name keyword

Example Prompts for Craft CMS (Craftnet) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Craft CMS (Craftnet) immediately.

"List all Craft CMS licenses in my account."

"Show me my recent plugin sales for this month."

"Search for plugins related to 'E-commerce' on Craftnet."

Troubleshooting Craft CMS (Craftnet) MCP Server with CrewAI

Common issues when connecting Craft CMS (Craftnet) 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.

Craft CMS (Craftnet) + CrewAI FAQ

Common questions about integrating Craft CMS (Craftnet) 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.