MindBridge MCP Server ⚡ The AI Router for Big Brain Moves

Created By
pinkpixel-deva year ago
MindBridge is an AI orchestration MCP server that lets any app talk to any LLM — OpenAI, Anthropic, DeepSeek, Ollama, and more — through a single unified API. Route queries, compare models, get second opinions, and build smarter multi-LLM workflows.
Overview

What is MindBridge MCP?

MindBridge MCP is an AI orchestration server that enables seamless communication between various applications and large language models (LLMs) like OpenAI, Anthropic, and DeepSeek through a unified API.

How to use MindBridge MCP?

To use MindBridge, install it via npm or clone the repository from GitHub. Configure your API keys for the desired LLMs, and start the server to begin routing queries and managing workflows.

Key features of MindBridge MCP?

  • Multi-LLM support for easy switching between different models.
  • Smart routing to models optimized for deep reasoning tasks.
  • Built-in tool for comparing responses from multiple models.
  • OpenAI-compatible API layer for easy integration.
  • Automatic detection of providers for hassle-free setup.
  • Highly configurable through environment variables and JSON.

Use cases of MindBridge MCP?

  1. Building multi-model AI workflows.
  2. Orchestrating complex reasoning tasks across different LLMs.
  3. Creating AI-powered applications without vendor lock-in.
  4. Facilitating second opinions by querying multiple models.

FAQ from MindBridge MCP?

  • Can MindBridge connect to any LLM?

Yes! MindBridge supports a variety of LLMs including OpenAI, Anthropic, and more.

  • Is there a cost to use MindBridge?

MindBridge is open-source and free to use under the MIT license.

  • How do I configure MindBridge?

Configuration is done through environment variables and a JSON file for MCP settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pinkpixel-dev
Star
10
Language
TypeScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago