A
licenseB
qualityD
maintenanceProduction-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.
15
41 npm
3
MIT
koba-mcp-bridge
Planned integration for Git workflows, enabling agents to manage repositories, branches, commits, and other version control operations.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@koba-mcp-bridgestart a Ghidra analysis on the firmware binary and save the findings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Briareus
Canonical GitHub repository: KobaProduction/briareus.
An independent-service, service-folder monorepo with modular MCP Hands, a thin routing Gateway and separate Control Panel API/UI.
NEW OWNER LAYOUT: Flat Services / Hands / Shared. IDENTITY/AUTH TARGET: Rauthy + Cedar. Four-agent executable migration: Backend / Runtime / Frontend / Deployment. Root AGENTS map: AGENTS.md.
Rauthy (upstream OAuth2/OIDC/MFA/SSO IdP) replaces custom Human Identity and homegrown OAuth. Existing Briareus Authorization remains owner of AgentSession grants, approvals/revocation and embeds Cedar PARC evaluation. Platform Control still owns Team and Project. Control Panel API is the independent management BFF for real IdP and other owner APIs; UI uses standard OIDC login. Gateway routes streams and calls Authorization directly for coarse MCP admission; each Hand independently enforces current Authorization grants for actual effects. The management API/UI never sit in the running MCP path.
Own service folder provides Docker/Compose/dependency lock, scoped Watch and native build; docs live outside source in docs/services mirrored structure. Reuse existing DB/Valkey volumes; untrusted Hands sandbox cannot reach private infrastructure and credentials. Native build + scoped Dev observation; no new generic test suites. Legacy Identity is retained as live transition only, not a parallel new OAuth implementation. Exact source and runtime statuses must be verified, not inferred from this documentation.
Folder rule: Internal service folders are flat services/api/, services/ui/, services/gateway/, services/authorization/, services/external/ (and other genuinely independent owners); MCP providers live only in root hands/<hand>/, shared small DTO/helpers in shared/. Each deploys from its OWN folder with its OWN Compose/Docker/lock and folder-only Watch. Legacy deploy/ stays rollback-only until physical cutover.
The existing External Services Coolify app packages upstream Rauthy with the PostgreSQL and Valkey vendor containers in services/external/; Cedar remains embedded in Authorization. Old deploy/data/ is retired as source only, without deleting its live data.
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessWithin a week
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.66MIT
- FlicenseNot gradedqualityDmaintenanceExposes MCP tools that enable remote LLMs to query local Docker containers, OS processes, and system services in real time.-
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.2 npmMIT