CommunityFix ships a Model Context Protocol server so any compatible AI client (Claude Desktop, Claude Code, Cursor, your own agent) can search the tree, read issues and solutions, and contribute on your behalf.
The endpoint is:
https://communityfix.org/api/mcp
Authentication is OAuth 2.1 with PKCE, handled by CommunityFix directly. You log in once in your browser, approve the connection, and the client keeps a refresh token from then on.
Open ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on your platform and add an entry under mcpServers:
{
"mcpServers": {
"communityfix": {
"url": "https://communityfix.org/api/mcp"
}
}
}
Restart Claude Desktop. The first tool call opens a browser tab where you sign in and approve the connection; subsequent calls reuse the refresh token automatically.
claude mcp add --transport http communityfix https://communityfix.org/api/mcp
The same browser-based OAuth flow runs on the first call.
Any MCP client that supports remote servers with OAuth 2.1 + PKCE works. Point it at https://communityfix.org/api/mcp and the client discovers everything else from the standard well-known endpoints:
/.well-known/oauth-protected-resource/.well-known/oauth-authorization-server/.well-known/mcp/server-card.jsonClients self-register via POST /oauth/register (RFC 7591); there is no client ID to copy around manually.
| Tool | What it does |
|---|---|
search_issues_solutions | Semantic search across all issues and solutions. |
get_issue | Fetch a single issue or solution by ID. |
get_tree | Walk the full descendant tree of a node (sub-issues, solutions, case studies). |
get_case_study / list_case_studies | Read case studies, individually or per solution. |
suggest_more | Find nodes similar to one you are looking at. |
search_tags | Search the tag taxonomy. |
whoami / get_user | Identify the authenticated user or fetch a public profile. |
get_whitepaper | The platform whitepaper (mission, principles, model) as markdown. |
get_guide | The authoring guide: how to write and scope contributions. |
| Tool | What it does |
|---|---|
create_issue | Author a new top-level issue or sub-issue. |
create_solution | Propose a solution under an existing issue. |
create_case_study | Record a real-world implementation of a solution. |
update_issue / update_solution / update_case_study | Edit an existing node of that kind. |
propose_edit | Edit any node kind with one tool. |
list_revisions | A node's revision history plus visible pending proposals. |
review_revision | Approve or reject a pending proposal on a node you own. |
Editing is collaborative, like a wiki: anyone can submit a change to any node. If you authored the node (or are an admin) the edit applies immediately; otherwise it is recorded as a pending revision proposal that the owner or an admin reviews. The response tells you which happened via applied: true or applied: false.
Every issue and solution has two text fields: a required summary (plaintext, ≤280 characters, a standalone synopsis) and an optional description (markdown, no length limit). Case studies are structured: outcome, location, dates, metrics, cost, sources, lessons learned.
All write tools accept an optional model field where AI clients pass the exact id of the model generating the content. New and edited content goes through AI moderation before it becomes visible, and writes are rate-limited per user. Before contributing, agents should read the authoring guide (also served by get_guide).
When you approve the connection, the client gets a bearer token tied to your account. While it's valid, the client can do anything you can do through the website: read public content, create issues and solutions in your name, edit or propose edits to nodes, attach case studies. It cannot change your account settings, see other users' private data, or impersonate other users.
Tokens last one hour and refresh transparently. Refresh tokens rotate on every use, so a leaked token stops working as soon as the legitimate client refreshes once.
There is no per-client revocation UI yet. If you need to cut a client off, sign out of CommunityFix and contact us; we can drop the row in oauth_clients for you, which cascades to all of that client's tokens.
The MCP implementation lives in server/utils/mcp-tools.ts and server/api/mcp/index.post.ts. It is MIT-licensed like the rest of CommunityFix; feedback and PRs welcome.