Documentation
Connect any MCP-capable assistant to ARRAG in three steps.
1 · Get an API key
Sign in with Discord, then generate a key on your dashboard. Keys are shown once and last up to 90 days. Copy it somewhere safe.
2 · The endpoint
https://mcp.horizonstudios.io/mcp
Transport: Streamable HTTP. Auth: Authorization: Bearer <key> (or an x-api-key header).
3 · Add it to your client
Claude Code
claude mcp add --transport http arrag https://mcp.horizonstudios.io/mcp --header "x-api-key: YOUR_API_KEY"
Cursor, Windsurf, and other mcp.json clients
{
"mcpServers": {
"arrag": {
"url": "https://mcp.horizonstudios.io/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
Replace YOUR_API_KEY with the key from your dashboard.
When a key expires (up to 90 days), your client will start getting
401 Unauthorized. Just generate a new key and update the header.What you can ask it to do
Once connected, your assistant can call these tools. You don't invoke them directly — just ask in natural language ("scaffold a replicated door component") and the assistant picks the right tools.
Knowledge & retrieval
ask_reforger — RAG answer grounded in the corpussearch_scripts — Full-text / semantic script searchdescribe_class — Members, methods, inheritance for a classget_script — Fetch a source file from the corpusSymbols
find_symbol — Locate a class/enum/member by nameclass_hierarchy — Ancestors + descendants of a classlookup_enum — Enum valuesattribute_reference — [Attribute()] editor-property referencegui_reference — Widget / layout referenceReplication (netcode)
plan_replication — Plan [RplProp]/[RplRpc] with failure-mode warningsexplain_replication — Explain a replication conceptfind_rpcs — Find RPCs by class / receiver / channelfind_replicated_props — Find replicated membersCodegen & validation
scaffold_component — Generate a ScriptComponentscaffold_gamemode — Generate a game modescaffold_useraction — Generate a ScriptedUserActionscaffold_ui — Generate a menu + layoutvalidate_enscript — Lint generated EnScriptGood practice
- Treat your API key like a password — don't commit it or paste it in shared chats.
- Use one key per machine/client so you can revoke just that one if needed.
- Revoke a key the moment a device is lost or a key leaks — it stops working instantly.
- For networking questions, let the assistant lean on
plan_replication; EnScript replication has silent failure modes.