mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-11-16 17:09:09 +00:00
Validated in the full merge-train on the .113 (lot 5, 2026-11-12): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change. Co-authored-by: Jowimila <127446097+jowimila@users.noreply.github.com>
title, version, lastUpdated
| title | version | lastUpdated |
|---|---|---|
| OmniRoute Integrations | 3.8.50 | 2026-09-13 |
OmniRoute Integrations
This directory contains documentation and configuration for integrating external services and tools with OmniRoute.
Available Integrations
MarkItDown MCP Server
Convert documents, PDFs, images, and web pages to markdown using the Microsoft MarkItDown MCP server.
- Status: ✅ Available
- Type: External Python MCP Server
- Documentation: MARKITDOWN_MCP.md
- Quick Start:
pip install markitdown-mcp npm run mcp:markitdown:http
Adding New Integrations
To add a new external MCP server integration:
- Create documentation in this directory (e.g.,
YOUR_SERVICE_MCP.md) - Add launch scripts in
scripts/integrations/(both.shand.mjsversions) - Add npm scripts in
package.jsonfor easy launching - Add requirements file if using Python (e.g.,
requirements-your-service.txt) - Update this README with a link to the new integration
Documentation Template
---
title: "Your Service MCP Integration"
version: X.Y.Z
lastUpdated: YYYY-MM-DD
---
# Your Service MCP Server Integration
> Brief description of what the service does.
## Installation
Installation instructions with package manager (pip/npm/cargo/etc).
## Running the Server
How to start the MCP server (STDIO and HTTP transports).
## Integration with OmniRoute
How to use the service with OmniRoute (if applicable).
...
Best Practices
- Use stdio transport by default for IDE integration (Claude Desktop, Cursor, Cline)
- Support HTTP transport for testing with MCP Inspector
- Document security implications and best practices
- Provide launch scripts in both Bash and Node.js
- Include troubleshooting section in documentation
- Test with MCP Inspector before documenting
Resources
Support
For issues with specific integrations, refer to the integration's documentation or the upstream project's repository.