Skip to main content

motleycrew

PyPI - Version CI

Website •︎ Documentation

Welcome to motleycrew, your ultimate framework for building multi-agent AI systems. With motleycrew, you can seamlessly mix and match AI agents and tools from popular frameworks, design advanced workflows, and leverage dynamic knowledge graphs — all with simplicity and elegance.

Think of motleycrew as a conductor that orchestrates a symphony of AI agents and tools. It provides building blocks for creating AI systems, enabling you to focus on the high-level design while motleycrew takes care of the rest.

Features

  • Integration: Combine AI agents and tools from Langchain, LlamaIndex, CrewAI, and Autogen. Use tools from Langchain and LlamaIndex, with more integrations coming soon.
  • Flexibility: Provide your agents with any tools or even other agents. All components implement Langchain's Runnable API, making them compatible with LCEL.
  • Advanced Flow Design: Design systems of any complexity by just coding a brief set of rules. Simply chain tasks together or utilize knowledge graphs for sophisticated flow design.
  • Caching and Observability: Built-in open-source observability with Lunary and caching of HTTP requests, including LLM API calls, with motleycache.

See our quickstart page for an overview of the framework and its capabilities.

Getting started

Installation

pip install motleycrew

First steps

To get you started, here's a simple example of how to create a crew with two agents: a writer and an illustrator. The writer will write a short article, and the illustrator will illustrate it.

from motleycrew import MotleyCrew
from motleycrew.agents.langchain import ReActToolCallingMotleyAgent
from motleycrew.tasks import SimpleTask
from motleycrew.tools.image.dall_e import DallEImageGeneratorTool
from langchain_community.tools import DuckDuckGoSearchRun

crew = MotleyCrew()

writer = ReActToolCallingMotleyAgent(name="writer", tools=[DuckDuckGoSearchRun()])
illustrator = ReActToolCallingMotleyAgent(name="illustrator", tools=[DallEImageGeneratorTool()])

write_task = SimpleTask(
    crew=crew, agent=writer, description="Write a short article about latest AI advancements"
)
illustrate_task = SimpleTask(
    crew=crew, agent=illustrator, description="Illustrate the given article"
)

write_task >> illustrate_task

crew.run()

print(write_task.output)
print(illustrate_task.output)

Here, we have a chain of two consecutive tasks. A SimpleTask basically just contains a prompt and an agent that will execute it. The >> operator is used to chain tasks together. If you want to learn more about creating flows in such fashion, see our blog with images example.

Knowledge graph and custom tasks

Under the hood, the tasks are stored in a knowledge graph, as well as all the data needed for their execution. You can create custom tasks that utilize the knowledge graph in any way you want. The graph can be used to control the flow of your system, or simply as a universal data store.

Please read our docs on key concepts and API to learn more about creating custom tasks and using the knowledge graph. Also, see how it all comes alive in the research agent example.

Caching and observability

We provide a universal HTTP caching tool, motleycache, also available as a separate package. It can cache all HTTP requests made by your agents, including LLM and tool calls, out of the box. This is especially useful for debugging and testing.

Motleycrew also comes with support for Lunary, an open-source observability platform. You can use it to monitor your agents' performance, visualize the flow of your system, and more.

To learn more about these features, see our caching and observability docs.

Examples

We have a small but growing collection of examples in our documentation.

  • For a working example of agents, tools, crew, and SimpleTask, check out the blog with images.
  • For a working example of custom tasks that fully utilize the knowledge graph backend, check out the research agent.

Support and contributions

We have a community Discord server where you can ask questions, share your ideas, and get help with your projects.

If you find a bug or have a feature request, feel free to open an issue in this repository. Contributions of any kind are also welcome!

Release files for motleycrew 0.3.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for motleycrew 0.3.7
File Size Uploaded
motleycrew-0.3.7.tar.gz 88.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for motleycrew 0.3.7
File Interpreter ABI Platform
motleycrew-0.3.7-py3-none-any.whl Python 3 none any Details

Total release size: 213.2 kB

Release files / motleycrew-0.3.7.tar.gz

Download URL motleycrew-0.3.7.tar.gz
Size 88.5 kB
Tags Source
SHA-256 checksum
How to use checksums
9e17588e480fc2d3a52204b7b1e1e61ef055e266c32d57cd65dafd033218d4d2
BLAKE2b-256 checksum
How to use checksums
c6842309e8fa83e096ea749f9a89ce6f08c4d2bc73a5ce2387d33fbec3e19d85
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 26, 2026.

Transparency log

Release files / motleycrew-0.3.7-py3-none-any.whl

Download URL motleycrew-0.3.7-py3-none-any.whl
Size 124.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fe509ea1de79eb48184cfc89b0d6827104bf79be65756c46dc1ae847b16491b0
BLAKE2b-256 checksum
How to use checksums
83480adb6d3d11f9c779cbd18b422570c095856402cc482418cea151cc2ff513
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.7 This release

2 release files

0.3.4

2 release files

0.3.3

2 release files

0.3.2

2 release files

0.3.0

2 release files

0.2.5

2 release files

0.2.4

2 release files

0.2.3

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.14

2 release files

0.1.13

2 release files

0.1.12

2 release files

0.1.11

2 release files

0.1.10

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page