Add RawTree plugin

[gnzjgo]

📕 Read CONTRIBUTING.md first — it's the rulebook (every
field, the quality bar, the Awesome Score). Reviewers cite it by rule number (G1–G8, UC-n, PL-n).

What this adds

Adds content/plugins/rawtree.md (plugin, status: proposed). Content-only PR: one new file under content/.

Disclosure (affiliation): I (Gonzalo, gnzjgo) am affiliated with RawTree. I'm a member of the rawtreedb GitHub org, so I'm submitting this as the scout (scouted_by: gnzjgo), not as the builder. The author is rmorehig, the top contributor to rawtreedb/rawtree-mcp, the public MIT-licensed MCP server. Access to RawTree is currently a private beta, and the listing says so (install step 1 and the body); it does not claim a free tier and has no pricing_note. The listing also warns that the OAuth connection grants broad access, including destructive operations, and says where to revoke it.

Icon: intentionally not included. The merge gate only allows additions under content/. A maintainer can run the icon script (scripts/fetch-plugin-icons-v2.mjs, which fetches from project_url), or I can supply the logo on request.

What I tested (2026-10-02): the hosted MCP at https://mcp.rawtree.com/mcp, end to end through a Grok Bot with OAuth sign-in. Read-only tools only: list-organizations, list-clusters, list-databases, list-tables, describe-table, run-query (a bounded count query) and list-logs all succeeded. I did not exercise any write or admin tools (insert, create/delete, cluster pause/resume, members, apps, API keys); the prompt gates all of those behind explicit approval.

npm run validate passes locally (1515 entries).

Checklist

• This PR adds exactly ONE new file under content/ (plus assets for this entry, if any). — content/plugins/rawtree.md; no assets.
• It follows CONTRIBUTING.md — required fields + the golden rules (G1–G8).
• npm run validate passes locally (schema, slug, vocabularies).
• slug is kebab-case and exactly matches the filename.
• I ran / used this myself end to end — it works today. — Hosted MCP + OAuth + the read-only tools above, tested 2026-10-02. Write/admin tools were not exercised.
• Every URL in the frontmatter resolves to real, relevant content. — project, docs, repo, both GitHub profiles and the X page return 200. https://mcp.rawtree.com/mcp is an MCP endpoint (it answers 401 to an unauthenticated request, as expected for OAuth), not a web page.
• The prompt body is the real, complete prompt — not a summary or a teaser.
• The entry body is plain markdown — no raw HTML (<script>, <iframe>, <style>, <form>, inline event handlers). CI rejects it (§8.5).
• I did NOT set verified_at or status: live — a maintainer sets those during verification (§10.1). (featured and sponsor are also not set.)
• This is not an ad. A listing that exists to funnel traffic to your product gets closed. Sponsor slots will exist for that — this isn't one. — My affiliation is disclosed above; the content describes what the MCP does and how to connect, and I'm happy to adjust wording if a reviewer sees promotional language.
• If this is someone else's work: author is the original creator, the origin is linked (source_url for a plugin, source_tweets[] for a use case), and scouted_by is me. — author: rmorehig (builder), scouted_by: gnzjgo, source_url links the official MCP docs.
• If the source is a YouTube video: ... — Not applicable, no YouTube source.
• I license this contribution under CC BY 4.0 (attribution: entry author + grokbot.dev).

Where it came from

• Product: https://rawtree.com
• Official MCP docs (source_url): https://rawtree.com/docs/reference/mcp
• Public MCP server repo (MIT): https://github.com/rawtreedb/rawtree-mcp

[scheemunai]

Merged into main (commit 178e3ec) and live now: https://grokbot.dev/plugins/rawtree/ 🎉

Maintainer edits were minimal — set status: live and stamped verified_at (2026-10-02). Everything else was already schema-clean: valid data/dashboards pair, install steps within limits, prompt well under cap. Thanks @gnzjgo for scouting and the write-up — the safety rails in the prompt (read-only by default, explicit approval before destructive ops, never echoing API keys) are exactly what we like to see.

Closing as merged.