Docs navigation
Docs / MCP Server Bridge

MCP Server Bridge

OpenSquilla can run as a stdio MCP server bridge for MCP-capable clients. Use this when another local AI client should call into OpenSquilla session workflows through the Model Context Protocol.

The MCP bridge is an integration surface. It is separate from OpenSquilla’s Web UI, CLI, channels, and gateway control console.

Requirements

The SDK 2.x implementation described here is included in this source checkout’s base installation. Install from source, or use an OpenSquilla release that includes the SDK 2.x migration; check its release notes before installing. Upgrading only the MCP SDK in an older OpenSquilla installation does not migrate the application.

Packaged installations use the MCP implementation shipped in the release wheel. For a source installation, follow Install from source. From the prepared checkout, install the core profile on macOS/Linux:

bash scripts/install_source.sh --profile core

On Windows:

powershell -ExecutionPolicy Bypass -File ./scripts/install_source.ps1 -Profile core

The recommended profile includes MCP as well. In this source version, existing installation commands that include the mcp extra remain accepted; the extra is a compatibility alias and adds no dependencies.

Start the OpenSquilla gateway:

opensquilla gateway run

Or use the managed gateway:

opensquilla gateway start --json
opensquilla gateway status

Run the Bridge

opensquilla mcp-server run

By default, the bridge connects to:

ws://localhost:18791/ws

Use a different gateway:

opensquilla mcp-server run --gateway ws://localhost:18792/ws

The command runs a stdio MCP server. Configure your MCP-capable client to launch that command as the server process.

Safety Notes

  • Keep the gateway bound to 127.0.0.1 unless you intentionally expose it.
  • Do not put provider keys or channel secrets in MCP client config examples.
  • Treat the MCP client as another tool-calling surface. The same OpenSquilla permissions, tools, sessions, and gateway state still matter.

Troubleshooting

If the bridge cannot start:

opensquilla gateway status
opensquilla doctor

If the command reports that MCP dependencies are missing, repair or reinstall OpenSquilla with its dependencies using the source installation steps above.

Read next:


Docs index · Product guide · Improve this page · Report a docs issue

Edit this page on GitHub OpenSquilla docs · synced from main