Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Docs, live API tools and prompts for the horizOn game backend in Godot, Unity and Unreal.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
HORIZON_API_KEY, HORIZON_ACCOUNT_API_KEY, HORIZON_BASE_URL비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"horizon": {
"command": "npx",
"args": [
"-y",
"horizon-mcp"
],
"env": {
"HORIZON_API_KEY": "your-value",
"HORIZON_ACCOUNT_API_KEY": "your-value",
"HORIZON_BASE_URL": "your-value"
}
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add horizon --env HORIZON_API_KEY=your-value --env HORIZON_ACCOUNT_API_KEY=your-value --env HORIZON_BASE_URL=your-value -- npx -y horizon-mcp실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"horizon": {
"command": "npx",
"args": [
"-y",
"horizon-mcp"
],
"env": {
"HORIZON_API_KEY": "your-value",
"HORIZON_ACCOUNT_API_KEY": "your-value",
"HORIZON_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"horizon": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"horizon-mcp"
],
"env": {
"HORIZON_API_KEY": "your-value",
"HORIZON_ACCOUNT_API_KEY": "your-value",
"HORIZON_BASE_URL": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
HORIZON_BASE_URL env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 ProjectMakersDE 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: HORIZON_API_KEY, HORIZON_ACCOUNT_API_KEY
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.9.1)은 15일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Starreel
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
MCP server for horizOn Backend-as-a-Service
Gives AI coding assistants documentation, live API tools, and workflow prompts for game and app development.
Add to your MCP client configuration (Claude Desktop, Cursor, etc.):
{
"mcpServers": { "horizOn": { "command": "npx", "args": ["-y", "horizon-mcp"], "env": { "HORIZON_API_KEY": "your-api-key-here" } } } }
The server exposes 29 documentation resources, 120 player tools and 4 workflow prompts. An Account Key enables additional scoped admin tools. These counts come from the registered MCP resources, tools and prompts.
Documentation resources are served directly from the MCP server. No API key required.
| URI | Description |
|---|---|
horizon://docs/marketplace | Atomic original-item escrow, exact prices, protected Inbox returns and scoped recovery. |
horizon://docs/chat | Direct/group/project text, metadata-only realtime, incremental snapshots, original receipts and scoped moderation. |
horizon://docs/matches | Opaque turn state, exact revisions, immutable reports, bounded deadlines and original ranked-run recovery. |
horizon://docs/shared-objects | Opaque bounded world data, current permissions, exact revisions and trusted ordinary game notices. |
horizon://docs/items | Unique inventory, bounded item properties and atomic server-owned purchases |
horizon://docs/groups | Guilds, roles, bounded member pages and revision-safe membership actions |
horizon://docs/friends | Atomic social relationships, explicit revisions and exact public friend-code lookup |
horizon://docs/achievements | Versioned definitions, permanent completion bits and immediate atomic value rewards |
horizon://docs/inbox | Session inbox, protected rewards, immutable broadcasts, server clock and safe publication retries |
horizon://docs/statistics | Atomic session counters, safe integer batches, explicit original IDs and cache/UTC recovery. SDK and admin examples |
horizon://docs/player-values | Atomic balances and offers, stable operation IDs, all three SDKs, safe retries and support corrections |
horizon://overview | What is horizOn, core concepts (Account vs User), features, tier system, API structure, and SDKs |
horizon://docs/auth | Authentication methods (Anonymous, Email, Google), endpoints, SDK code examples, and common errors |
horizon://docs/leaderboard | Leaderboard score submission, top entries, user rank, entries around user, player profile per entry, validated only boards, with SDK examples |
horizon://docs/cloud-save | Cloud save/load for JSON and binary data, tier size limits, SDK examples |
horizon://docs/remote-config | Server-side key-value configuration: feature flags, game balance, A/B testing. SDK examples |
horizon://docs/localization | Server-side localized strings across 15 languages: per-key translations, single/all fetch, available languages. SDK examples |
horizon://docs/news | In-game news and announcements with language filtering. SDK examples |
horizon://docs/gift-codes | Gift code validation and redemption, cosmetic grants, server-owned value rewards, compact V2 original intents and exact counter strings. SDK examples |
horizon://docs/player-profile | Player avatar, frame and badges from a per-project cosmetics catalog, unlocks via gift code grants, profile in leaderboard entries. SDK examples |
horizon://docs/validated-actions | Server-checked runs: single-use run tickets with a server seed, SHA-256 input log hash, server-only rules, validated only leaderboards, server-owned player state, start context, evidence upload, admin evidence review with sus packages and package export, rejection codes. SDK examples |
horizon://docs/feedback | Bug reports, feature requests, and general feedback submission. SDK examples |
horizon://docs/user-logs | Server-side event and error tracking. Requires BASIC tier or higher. SDK examples |
horizon://docs/crash-reporting | Crash report submission, session tracking, fingerprinting, breadcrumbs, and auto-regression detection. SDK examples |
horizon://api/reference | Complete API reference for all horizOn App API endpoints with request/response schemas |
horizon://quickstart/godot | Step-by-step guide to integrate horizOn in Godot with GDScript examples |
horizon://quickstart/unity | Step-by-step guide to integrate horizOn in Unity with C# examples |
horizon://docs/email-sending | Transactional and event-based email delivery to registered users. Templates, scheduling, status tracking, and SMTP integration. SDK examples |
horizon://quickstart/unreal | Step-by-step guide to integrate horizOn in Unreal Engine 5.5+ with the official horizOn SDK plugin. C++ and Blueprint examples |
Live API tools that call the horizOn backend. Requires a valid API key.
horizon_submit_score, horizon_save_cloud_data, horizon_load_cloud_data, horizon_prepare_gift_code, horizon_redeem_gift_code, horizon_get_profile, horizon_set_profile, horizon_start_run, horizon_submit_validated, horizon_get_state and horizon_upload_evidence also need the player's session: sign in first and pass the returned accessToken as sessionToken.
The four player-value tools also require the same player session. Never generate another operation ID automatically after an uncertain result.
Every tool declares MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint), so clients can tell reads from writes. Examples of destructive tools include horizon_save_cloud_data (replaces the save), horizon_set_profile (replaces the whole profile), horizon_submit_validated (consumes the ticket, can spend balances) and horizon_cancel_email, plus horizon_purchase_player_value_offer and horizon_adjust_player_value (debit or credit exactly once per persisted operation ID). Many read tools that return an object also declare an outputSchema and return structuredContent next to the JSON text. Each description names when to use the tool, which sibling to use instead, what it returns and how to recover from its errors.
| Tool | Description |
|---|---|
horizon_test_connection | Test connection to the horizOn API (health check) |
horizon_signup_anonymous | Create a new anonymous user account |
horizon_signup_email | Create a new user account with email and password |
horizon_signin_email | Sign in with email and password |
horizon_signin_anonymous | Sign in with an anonymous token |
horizon_check_auth | Check whether a user session is still valid |
horizon_list_leaderboards | List available leaderboard boards for multi-board calls |
horizon_submit_score | Submit a score to the leaderboard (403 VALIDATED_SUBMIT_REQUIRED on validated only boards) |
horizon_get_leaderboard_top | Get the top leaderboard entries with each player's profile, optionally by board key |
horizon_get_user_rank | Get a user's leaderboard rank, optionally by board key |
horizon_get_leaderboard_around | Get leaderboard entries around a user's position, optionally by board key |
horizon_save_cloud_data | Save cloud data for a user, optionally only at an expectedRevision (409 on conflict) |
horizon_load_cloud_data | Load cloud save data for a user, with its revision |
horizon_get_remote_config | Get a single remote config value by key |
horizon_get_all_remote_configs | Get all remote config values |
horizon_get_localization | Get a single localized string by key, optionally for a specific language |
horizon_get_all_localizations | Get all localized strings, optionally for a specific language |
horizon_get_localization_languages | List the languages that have localizations for the app |
horizon_get_news | Get news articles with optional language filtering |
horizon_validate_gift_code | Validate a gift code without redeeming it |
horizon_prepare_gift_code | Read-only V2 preparation; persist all seven original intent fields before consume |
horizon_redeem_gift_code | Explicit consume/retry of that saved intent; current state on replay, no automatic replacement or V1 translation |
horizon_get_profile | Get a player's profile (avatar, frame, badges), unlocks and the cosmetics catalog |
horizon_set_profile | Replace a player's whole profile (avatar, frame, up to 3 badges) |
horizon_get_player_values | Read balances and operation window with the active player session |
horizon_get_player_value_offers | Read configured offers for the player |
horizon_purchase_player_value_offer | Purchase atomically with a caller-persisted operation ID |
horizon_adjust_player_value | Adjust within explicitly enabled limits with a stable ID and reason |
horizon_start_run | Start a server-checked run: single-use ticket with a server seed, optionally bound to a board and with a start context (game, content, simulation and replay format versions, content digest, initial state as base64) |
horizon_submit_validated | Submit a run result with the ticket and the SHA-256 input log hash (given, or computed locally from base64 bytes or text), optionally with earned server-owned values; returns sus (accepted but over a soft threshold); rejections name their code |
horizon_get_state | Read the player's server-owned values (balance, earned today, daily cap per value key); read only |
horizon_upload_evidence | Upload the input log (text or base64, encoded locally) of a run whose submit result asked for evidence; rejections name their code |
horizon_get_statistics | Reads a player's statistics snapshot and server operation window. |
horizon_get_statistics_definitions | Reads the project's statistics catalog conditionally by version. |
horizon_update_statistics | Applies one explicit atomic session batch with a caller-persisted operation ID. |
horizon_get_achievements | Reads visible achievement definitions and permanent completion bits. |
horizon_unlock_achievement | Unlocks one configured manual achievement once for the authenticated player. |
horizon_deliver_achievement_rewards | Reads compatibility reward status for up to eight original achievement keys. |
horizon_get_friends | Reads friends, incoming/outgoing requests, blocks and current limits. |
horizon_find_player | Finds one public player by exact UUID or canonical H- friend code in this project. |
horizon_send_friend_request | Sends Friend Request using the reviewed player revision. |
horizon_accept_friend_request | Accepts Friend Request using the reviewed player revision. |
horizon_decline_friend_request | Declines Friend Request using the reviewed player revision. |
horizon_cancel_friend_request | Cancels Friend Request using the reviewed player revision. |
horizon_remove_friend | Removes Friend using the reviewed player revision. |
horizon_block_player | Blocks Player using the reviewed player revision. |
horizon_unblock_player | Unblocks Player using the reviewed player revision. |
horizon_get_groups | Reads my groups using a matching player session. |
horizon_get_group | Reads group using a matching player session. |
horizon_get_group_members | Reads group members using a matching player session. |
horizon_get_group_pending | Reads group pending requests using a matching player session. |
horizon_create_group | Creates a fresh server-identified group and its leader atomically. |
|
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요