Moxie MCP Server for CrewAIGive CrewAI instant access to 12 tools to Create Client, Create Expense, Create Invoice, and more
Connect your CrewAI agents to Moxie through Vinkius, pass the Edge URL in the `mcps` parameter and every Moxie tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.
Ask AI about this App Connector for CrewAI
The Moxie app connector for CrewAI is a standout in the Productivity category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
from crewai import Agent, Task, Crew
agent = Agent(
role="Moxie Specialist",
goal="Help users interact with Moxie effectively",
backstory=(
"You are an expert at leveraging Moxie 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 Moxie "
"and summarize their capabilities."
),
agent=agent,
expected_output=(
"A detailed summary of 12 available tools "
"and what they can do."
),
)
crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
* 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 Moxie MCP Server
Connect your Moxie workspace to any AI agent and manage your freelance or agency business through natural conversation.
When paired with CrewAI, Moxie becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Moxie 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
- Clients & Contacts — List clients, create new ones, search contacts
- Projects & Tasks — Search/create projects, create tasks
- Invoices — Search payable invoices, create new ones
- Time & Expenses — Log time entries, record expenses
- Tickets — Create support tickets
- Users — List workspace team members
The Moxie MCP Server exposes 12 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 12 Moxie tools available for CrewAI
When CrewAI connects to Moxie through Vinkius, your AI agent gets direct access to every tool listed below — spanning freelance-management, invoicing, time-tracking, 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 a new client
Log an expense
Create a new invoice
Create a new project
Create a new task
Create a support ticket
Log time
List all clients in Moxie
List workspace users
Search for contacts
Search for payable invoices
Search for projects
Connect Moxie to CrewAI via MCP
Follow these steps to wire Moxie into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Install CrewAI
pip install crewaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.comCustomize the agent
role, goal, and backstory to fit your use caseRun the crew
python crew.py. CrewAI auto-discovers 12 tools from MoxieWhy Use CrewAI with the Moxie MCP Server
CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Moxie 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
Moxie + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Moxie MCP Server delivers measurable value.
Automated multi-step research: a reconnaissance agent queries Moxie 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 Moxie, analyzes trends over time, and generates executive briefings in markdown or PDF format
Multi-source enrichment pipelines: chain Moxie 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 Moxie against predefined policy rules, generates deviation reports, and routes findings to the appropriate team
Example Prompts for Moxie in CrewAI
Ready-to-use prompts you can give your CrewAI agent to start working with Moxie immediately.
"List all clients and their projects."
"Log 2 hours of consulting on the Acme Corp project."
"Create an invoice for Beta Design."
Troubleshooting Moxie MCP Server with CrewAI
Common issues when connecting Moxie to CrewAI through the Vinkius, and how to resolve them.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Moxie + CrewAI FAQ
Common questions about integrating Moxie MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.