⛔ #32 feat(mcp): add Connectors - URL+headers and OAuth 2.1 +3,100 -6 4mo ago by
ZachLaik ↗ analysis ↗ GitHub ## Summary
ZachLaik/mike
A settings-led take on Mike that lets users bring their own external tools into chat.
ZachLaik's fork is exploring a more extensible Mike: users could connect their own external services from settings and make those tools available in chat.
The direction is practical integration rather than a new legal-practice niche. ZachLaik is the named owner; no further identity information is available. OAuth 2.1 sign-in is part of the proposed connector experience, suggesting an eye toward services that require managed access.
What's in it
- User-managed connectors Add external services from settings instead of requiring a product-specific build.
- Chat tool access Make enabled connector tools available when using the chat assistant.
- OAuth 2.1 sign-in Support sign-in for external services that require authenticated access.
Direction
integrationworkflowsecurity
Activity
📝 ZachLaik wires Mike into outside tools, no engineer required 3 commits 6mo ago integrationworkflow draft
A new Connectors feature lets users bolt their own external services onto Mike from a settings page, without touching the codebase.
Threads of work (detailed view)
ZachLaik wires Mike into outside tools, no engineer required
A new Connectors feature lets users bolt their own external services onto Mike from a settings page, without touching the codebase.
User-configurable MCP connectors with OAuth 2.1, built into Mike's chat
ZachLaik's Connectors feature lets users register their own MCP servers from a Settings tab - URL plus optional headers, or a full OAuth 2.1 flow for spec-conformant servers - with tools from each enabled connector automatically merged into the chat assistant's per-request tool list.
Pull requests (detailed view)
⛔ Closed without merge (1)
by
ZachLaik · opened 6mo ago · closed 4mo ago