⛔ #32 feat(mcp): add Connectors - URL+headers and OAuth 2.1 +3,100 -6 26d ago by
ZachLaik ↗ analysis ↗ GitHub ## Summary
ZachLaik/mike
ZachLaik is adding a Connectors settings page so firms can plug their own outside tools into Mike's assistant themselves.
This fork is about one thing: letting people wire their own tools into Mike without calling a developer. ZachLaik has been building a Connectors feature - open a settings page, add an external service, sign in with OAuth 2.1, and Mike's chat assistant can use it. The fork's own code never needs touching, which is the point.
Both threads MikeWatch has tracked so far circle this same idea, first as a proposal and then as a working settings-page feature built on user-configurable MCP connectors. There's no rebrand and no wider product story yet. The pitch is squarely at firms that already have services they want Mike to reach.
On identity, the public record is thin: a handle, this fork, and little else. The work went quiet after early May 2026, so if the connector idea interests you, the GitHub threads are where the substance lives.
What's in it
- Bring-your-own connectors A settings page where users add outside services to Mike's chat assistant on their own. No engineer, no code changes.
- OAuth 2.1 sign-in Each connected service is authorized through a standard OAuth 2.1 sign-in flow.
- No-engineering setup Firms configure everything from the product itself; extending Mike stops being a development project.
Direction
integration
Activity
📝 ZachLaik wants to let firms bolt their own tools onto Mike 3 commits 2mo ago integrationchat-ui draft
A proposal to make Mike's chat assistant extensible by users, with no engineering required on the fork itself.
📝 ZachLaik wires Mike into outside tools, no engineer required 3 commits 2mo ago integrationworkflow draft
A new Connectors feature lets users bolt their own external services onto Mike from a settings page, without touching the codebase.
🟢 #32 feat(mcp): add Connectors - URL+headers and OAuth 2.1 +3,100 -6 2mo ago by
ZachLaik ↗ analysis ↗ GitHub ## Summary
Threads of work (detailed view)
ZachLaik wants to let firms bolt their own tools onto Mike
A proposal to make Mike's chat assistant extensible by users, with no engineering required on the fork itself.
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)
🟢 Open (1)
by
ZachLaik · opened 2mo ago ⛔ Closed without merge (1)
by
ZachLaik · opened 2mo ago · closed 26d ago