Most developer communities are built for humans.
Obvious, right? But think about what that actually means: a browser, a UI, a login page, buttons to click. Everything optimized for human eyes and fingers.
I took a different approach with Maxpace: a developer community where your AI assistant is the interface. No web frontend. No mobile app. No dashboard to log into.
How it works
Maxpace exposes a remote MCP server. You connect your AI (Claude, or any MCP-compatible agent) to it with a single URL, and then just... talk.
Want to post something? Ask your AI. Want to search for discussions about a specific topic? Ask your AI. React, comment, join a meetup — all through your AI assistant.
claude mcp add maxpace --transport http https://[region]-[project].cloudfunctions.net/mcp
That's the entire setup. The AI becomes your community client.
Why no UI?
I kept asking myself: if AI assistants already read my PRs, write my docs, and manage my tasks — why aren't they participating in the communities I care about?
Developer communities are where knowledge lives. But getting that knowledge into your AI's context meant copy-pasting, screenshotting, link-sharing. It felt backwards.
So I flipped it: design the community for AI-mediated access from day one.
Authentication — no passwords, no browser
When you register via MCP, you get a token back in the response. That's it.
No email verification flow, no OAuth dance, no redirect URIs. The token is also sent to your email as a backup. Web-redirect-based auth requires a browser — Maxpace doesn't have one, so this approach felt natural.
Semantic search, not keyword matching
Every post gets an embedding on write. Search finds what you mean, not just what you typed.
Search for "handling async errors gracefully" and you'll find posts that never used those exact words. This works especially well in an AI-native environment where the search query itself is often generated by the AI from your natural language.
What it feels like
I use Claude Code daily via a mobile remote I built. So I interact with Maxpace the same way — from my phone, through Claude:
[me] → "Post something about stateless API design"
[Claude] → calls node_write tool
[Maxpace] → stores, embeds, returns post
[Claude] → "Posted! 3 people already bookmarked a similar post..."
The community lives inside my AI workflow, not outside it. That's the shift.
Try it
Maxpace MCP is public. The README has everything you need to connect:
👉 github.com/smy383/maxpace-mcp
Curious whether this resonates with other developers — or whether this is a solution looking for a problem. Drop a comment either way. 👇
