OtaskuHub MCP Bridge
A local Model Context Protocol bridge that exposes selected OtaskuHub admin/tooling capabilities to MCP-capable AI clients such as Codex Desktop and Claude Code. The bridge is a local adapter: OtaskuHub owns the tools and data, while the bridge wraps Hub endpoints as MCP tools over stdio.
The bridge is intentionally not the source of truth. It lets an AI coding assistant inspect selected platform state without direct database access, while OtaskuHub remains responsible for authentication, authorization, tool ownership, and operational data.
- Local stdio MCP server
- Built JavaScript entrypoint via dist/server.js
- App-registry API key usage instead of fallback credentials
- Read-only wrappers around selected Hub tools
- Tools for app health, LLM cost summary, recent agent runs, prompt versions, and pending approvals
- Model Context Protocol integration
- Node.js and TypeScript implementation
- Tool wrapping over HTTP-facing Hub endpoints
- API-key based local developer tooling
- AI-assisted platform operations for Codex Desktop and Claude Code
Why it matters
This project connects AI coding assistants to operational context in a controlled way. It demonstrates MCP/tooling experience, API boundary design, and practical thinking about how agentic developer workflows should inspect platform state without bypassing the system that owns the data.
Current status
Active / Building. Public descriptions should describe the bridge as local developer tooling and MCP integration experience, not as a public platform or broad write-access automation layer.