claude mcp add getabrain-mcp-server -- npx -y getabrain-mcp-server
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
0 ★ · Guitarmaniac24/getabrain-mcp-server · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository Guitarmaniac24/getabrain-mcp-server;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
MCP server for GetABrain.ai — give your AI agent real human judgment as native tools. Use with Claude Desktop / Cursor Add to your MCP client config (e.g. claude_desktop_config.json): Get your API key by signing up at https://getabrain.ai. Remote (hosted) MCP server -- no install Prefer not to run anything locally? GetABrain also hosts this same server over Streamable HTTP at https://www.getabrain.ai/api/mcp. Point any MCP client that supports remote servers at that URL and pass your key pair as headers instead of env vars: Same 7 tools, same schemas, same test-mode support -- see docs/deploy/remote-mcp.md in this repo for details (Smithery-style clients, auth requirements, etc). Test mode Test mode is a flag on the key, not a different key format. When you mint an API key — via POST /api/v1/requestor/keys with {"mode":"test"}, or by choosing "test" in the dashboard — you get back a completely normal gab_k_… / gab_s_… key pair. There's no _test_ in the string; the test-ness lives in the database as an is_test flag on that key. No funding or card required. Point GETABRAIN_API_KEY / GETABRAIN_API_SECRET at a test-mode key and the server behaves identically, except: - submit_query never touches your balance — no charge, no insufficient_balance errors. - Responses come back synthetic and are always marked **simulated: true**, so your pipeline (submit → wait/poll → rate) can be built and exercised end-to-end before any real human worker or real money is involved. - get_balance reports mode: "test" so the agent/human can tell at a glance which environment it's in. When you're ready to go live: mint a **live-mode key** (same call, {"mode":"live"} or the dashboard default), fund the account with create_topup_link (works with either key type — a test-mode agent can generate the link, a human completes checkout to add real funds), and swap the env vars. get_balance then reports mode: "live", and submit_query starts spending real balance and dispatching to real paid workers. Tools - get_balance — read-only: prepaid balance (cents), mode ("test"/"live"), and auto_reload_enabled (with a setup link + hint when it's off and would otherwise stall a live account at zero balance). - create_topup_link — mints a Stripe Checkout URL to add funds (min $5); a human opens it in a browser to pay — the agent cannot complete payment itself. - submit_query — ask real humans a question (16 query types: A/B test, rating, ranking, sentiment, yes/no, image/video/audio review, voice/video/photo capture, …). Returns a query_id. Spends balance on a live key; free and simulated: true on a test key. - get_responses — one-shot, read-only: current status + whatever responses exist right now, no waiting.