Skip to content
Back to the index

mcpipe

PyPIInfrastructure

PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 30 Jun 2026. How this is checked

mcpipe is an open-source, plugin-based MCP server framework that allows developers to route any CLI tool through customizable Source → Executor → Sink pipelines. It supports the Model Context Protocol and is designed for extensibility and integration with other tools.

Inferred · not functionally tested

Open SourceMITCLISelf-hosted
Visit PyPI

Overview

5 features

Purpose: Enabling developers to route and orchestrate CLI tools through flexible, plugin-based pipelines using the MCP protocol.

Inferred · not functionally tested

Audience: developers

Inferred · not functionally tested

Functions: workflow_automation

Inferred · not functionally tested

Interfaces: API: unknown · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: pypi.org · github.com. These links do not verify the individual claims.

mcpipe sits in PulseGate's Frameworks & runtimes category. Inferred · not functionally tested: Enabling developers to route and orchestrate CLI tools through flexible, plugin-based pipelines using the MCP protocol. Inferred · not functionally tested: mcpipe is an open-source project aimed at developers. Basis unknown · not verified: mcpipe is open source under the MIT license. Basis unknown · not verified: It runs on the command line, and it can be self-hosted.

mcpipe first shipped in 2026. Inferred · not functionally tested: Key capabilities include plugin architecture, pipeline routing, and CLI integration. Basis unknown · not verified: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Plugin architecture
  • Pipeline routing
  • CLI integration
  • MCP protocol support
  • Extensible plugins

Topics: Inferred · not functionally tested

Tags
mcp-servercli-pipelineplugin-framework

JSON profile · Text profile · Access guide

Built with & integrations

Connectors
MCP
Runs on
CLISelf-hosted

Trust & compliance

License
MIT
Public signals
HTTPSOpen SourceGitHub

Indexing history

What PulseGate has recorded for this listing

Nothing recorded for this listing in this window.

Frequently asked questions about mcpipe

What is mcpipe?
Inferred · not functionally tested: Enabling developers to route and orchestrate CLI tools through flexible, plugin-based pipelines using the MCP protocol. It is catalogued under Frameworks & runtimes on PulseGate.
Who should use mcpipe?
Inferred · not functionally tested: mcpipe is an open-source project built for developers.
Does mcpipe have a free plan?
Basis unknown · not verified: Yes — mcpipe is open source under the MIT license and free to use.
What platforms does mcpipe run on?
Basis unknown · not verified: mcpipe runs on the command line. It can also be self-hosted.
Is mcpipe still active?
PulseGate's liveness check found it on 13 Sep 2026.
What are alternatives to mcpipe?
Similar projects tracked by PulseGate include pipen-mcp, pycli-mcp, and portage-mcp.pipen-mcppycli-mcpportage-mcp
When did mcpipe launch?
mcpipe first shipped in 2026.
Is mcpipe open source?
Basis unknown · not verified: Yes — mcpipe is open source under the MIT license, developed on GitHub.

Similar projects

Closest matches by what these projects do