What is Pipelex Mcp

pipelex-mcp is the Model Context Protocol server designed for the Pipelex ecosystem, enabling AI Agents to run Pipelex pipelines as native tools in their toolset.

Use cases

Use cases for pipelex-mcp include automating data workflows, enhancing AI agent capabilities with structured processing, and integrating complex pipeline executions into applications.

How to use

To use pipelex-mcp, install it following the provided installation instructions, ensure prerequisites are met, and then utilize the API to discover and execute pipelines with specific inputs.

Key features

Key features of pipelex-mcp include the ability for AI agents to discover available pipelines, execute them with specific inputs, and receive structured outputs that are easy to understand and utilize.

Where to use

pipelex-mcp can be used in various fields including AI development, data processing, and automation, where integration of structured pipelines is beneficial.

📑 Table of Contents

• Introduction
• Quick Start
  • Prerequisites
  • Installation
• Adding New Tools
• Known Limitations
• Contributing
• Support
• License

Introduction

👉 Check out our main repository to learn more about Pipelex!

The Model Context Protocol (MCP) is a specialized component of the Pipelex ecosystem that enables AI Agents to interact with Pipelex pipelines as native tools. This protocol bridges the gap between AI agents and the structured, reliable pipeline execution that Pipelex provides.

MCP allows AI agents to:

• Discover available pipelines
• Execute pipelines with specific inputs
• Receive structured outputs in a format they can understand and use

To learn more about MCP itself, check out the official MCP documentation from Anthropic.

🚀 Quick Start

Prerequisites

• Python >=3.11,<3.12
• uv package manager

Installation

1. Clone the repository:

git clone https://github.com/Pipelex/pipelex-mcp.git
cd pipelex-mcp

2. Install dependencies:

make install

3. Set up your environment:

cp pipelex_mcp/.env.example pipelex_mcp/.env
# Edit pipelex_mcp/.env with your configuration

4. Add your API keys:
   Configure your API keys in the .env file. These will be used by the MCP server to authenticate with various services.

MCP Clients

Cursor

Cursor comes with built-in MCP support. Simply describe the tool you want to use in the chat, and Cursor will automatically invoke it.

Learn more about MCP in Cursor

Claude Desktop

Claude Desktop uses its own configuration format. Check the MCP documentation for setup details:

Claude Desktop MCP Setup Guide

Other Clients

MCP is an open protocol - any client that implements the protocol can interact with MCP servers. Check the MCP documentation for a full list of available clients.

🛠 Adding New Tools

Adding a new tool (pipe) to the MCP server is straightforward. Here’s a basic example:

@mcp.tool("generate_company_mascott")
async def generate_company_mascott(company_context: str) -> dict:
    """Generate multiple mascot options for a company using the complete design process.
    Output the links of the images.
    
    Args:
        company_context: Context about the company
        
    Returns:
        dict: Response containing generated mascot images
    """
    # Your implementation here
    return {"images": [...]}

Key points when adding a new tool:

1. Use the @mcp.tool decorator with a unique name
2. Define clear input parameters with type hints
3. Write a comprehensive docstring explaining the tool’s purpose
4. Return structured data that the AI agent can understand

For more complex examples and to understand the underlying Pipelex technology, check out the Pipelex Documentation.

⚠️ Known Limitations

We are actively working on improving these aspects of the repository:

Library Duplication

Currently, the pipelex_libraries folder needs to exist in two locations:

• At the root of the project
• Inside the pipelex_mcp folder

This duplication is not ideal and we’re working on a better solution for managing shared libraries.

Logging Configuration

The current logging system has some limitations:

• Difficulty in redirecting logs to specific files
• Limited control over log formatting and destinations
• No built-in log rotation or management

We’re planning to implement a more robust logging system in future updates.

Long-Running Pipelines

For pipelines that take longer than the MCP client timeout to complete, we need to implement a session ID system. This would allow:

• Handling of timeouts gracefully
• Resuming pipeline execution
• Status tracking for long-running operations

This feature is planned for future releases to better support extended pipeline operations.

🤝 Contributing

We welcome contributions! Please check our issues page or submit a pull request.

💬 Support

• GitHub Issues: For bug reports and feature requests
• Discussions: For questions and community discussions
• Documentation

📝 License

This project is licensed under the MIT license.

---

“Pipelex” is a trademark of Evotis S.A.S.

© 2025 Evotis S.A.S.