27-0-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@27-0-mcptell me the rules of 27-0"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
27-0 MCP Server
27-0 NRL Game - Build the Perfect XIII, Go Undefeated
A Model Context Protocol server that exposes the canonical 27-0 knowledge surface — game rules, roster constraints, and entry points, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.
Official website: https://27-0game.com
🎮 About 27-0
27-0 is a free browser game for NRL fans who want to build an all-time rugby league XIII and see whether it can survive a perfect season. The site turns an ordinary greatest-player debate into a constrained draft: each round spins an NRL club and era, then the player chooses one eligible legend for the open position. After thirteen picks, the lineup is run through a seeded 27-round season simulation. The goal is an undefeated 27-0 record and the highest available grade, not a prediction of a real NRL result.
Related MCP server: 17-0 MCP Server
Key Features
Fixed 13-player lineup — The roster follows the NRL jersey structure: fullback, two wings, two centres, five-eighth, halfback, two props, hooker, two second-rowers, and lock. A pick must fit the position currently open, so famous names alone cannot solve the draft.
Club-and-era spins — Every selection starts from a historical club and era pool. Players choose from the legends eligible for that spin instead of searching an unrestricted database.
27-round simulation — A completed XIII is evaluated across 27 rounds, with regular-season and finals stages leading to a grand final. The simulation is deterministic for a given seed and roster, which makes shared runs reproducible.
Three draft experiences — Classic keeps player stats visible for number-based decisions. Daily uses the same thirteen spins for everyone, allows one attempt, and resets at midnight AEST. Footy IQ hides the stats so the draft relies on memory and rugby knowledge.
Leaderboards and share codes — Players can submit a result to the leaderboard and share a compact code that recreates the run. Leaderboard entries are user-submitted game results, not certified competitive records. The public pages include the play screen, daily challenge, leaderboard, and share routes.
Free and independent — The game runs in a browser without an account requirement for play. It is an independent fan project and is not affiliated with the NRL or any club. Player names, statistics, and ratings are site-curated game data used for commentary and parody, not official NRL records.
Use Cases
NRL fans can use Classic to compare the game's displayed player profiles, use Footy IQ to test historical knowledge, or return to Daily for a shared challenge. A group can play the same daily seed, post the resulting record, and open a share link to inspect the lineup and round-by-round story. The fixed positions create meaningful trade-offs between backs, forwards, spine roles, and the strength of each club-era pool.
Who Is It For
27-0 is for rugby league supporters who enjoy all-time debates, roster builders, daily games, and short competitive sessions. It is designed to be completed in a few minutes on desktop or mobile. The simulation is an entertainment mechanic: it should not be read as an official ranking of players, clubs, or likely real-world match outcomes.
Tools
get_game_rules
Return the verified game rules, roster constraints, and public entry points the site exposes. (27-0)
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for 27-0 (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://27-0/rules— Verified game rules, roster-building constraints, and public entry points.site://27-0/faq— Short FAQ generated from public site metadata.site://27-0/links— Canonical URLs to share with users.
Prompts
tell_me_about_27_0
Summarize what the site is, who it's for, and how it works. — 27-0
plan_a_run_27_0
Plan a single play-through using verified rules and entry points. — 27-0
Installation
Install via Smithery
npx -y @smithery/cli install 27-0-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/Rocniubi/27-0-mcp.git
cd 27-0-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"27-0-mcp": {
"command": "node",
"args": [
"/absolute/path/to/27-0-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://27-0game.com
Support: hello@27-0game.com
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
2 toolsget_game_rulesA
Return the verified game rules, roster constraints, and public entry points the site exposes. (27-0)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description adds context by noting the data is 'verified' and lists three categories of returned information. However, it omits details like safety, idempotency, or caching behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no wasted words. It is front-loaded with the action and clearly lists what is returned.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters and no output schema, the description adequately conveys the purpose and content. It could mention the format or structure of the return value, but the current level is sufficient for a simple query.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and schema coverage is 100%, so no parameter explanation is needed. The description appropriately focuses on the return value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Return' and specifies the resources: 'verified game rules, roster constraints, and public entry points.' It distinguishes from sibling tool 'get_official_links' by implying different content.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus the sibling 'get_official_links' or any other context. The description does not mention prerequisites or scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_official_linksA
Return the canonical list of official links for 27-0 (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description is minimal and does not disclose behavioral traits like caching, permission needs, or return format. For a zero-annotation tool, more context is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no extraneous words. Clearly communicates purpose immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple tool with no parameters, but lacks details on return format, '27-0' context, and edge cases. Could be more complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters, so baseline 4. Description adds no parameter info, but schema is empty; no additional meaning needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states verb 'Return' and resource 'canonical list of official links for 27-0', listing types (website, support, docs). Distinct from sibling 'get_game_rules' which focuses on rules.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage for retrieving official links, but no explicit guidance on when to use over sibling or alternatives. No exclusions or context provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
v0.1.0- First observed
get_game_rules - First observed
get_official_links
TDQS
The two tools have distinctly different purposes: one returns game rules, the other returns official links. There is no overlap in functionality.
Both tools follow a consistent 'get_' prefix followed by a noun describing the resource. The naming pattern is uniform.
With only two tools, the server feels minimal. While the tools are appropriate for a simple information retrieval server, the number is at the low end of the acceptable range for a game-related MCP.
The server only provides static information retrieval. For a game MCP, one would expect additional tools for player interaction, game state management, or rule lookup by topic. The lack of such features creates significant gaps.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Read-only MCP tools for AI agent discovery, structured resources, and NIULAI information.
Knowledge base MCP for AI agents on iknow.dev. Search, read, and maintain via OAuth.
Read-only game, setup, place, evidence and travel decision tools with explicit provenance.
- FlowdexOAuthdk.flowdex
Read and write your team's shared, AI-readable wiki from any MCP client.
Related MCP Servers
- AlicenseAqualityCmaintenanceExposes the canonical 7-0 knowledge surface — game modes, roster picks, and scenarios, FAQ, official links2MIT
- AlicenseAqualityCmaintenanceExposes the canonical 17-0 knowledge surface including game rules, roster constraints, and entry points for the NFL roster strategy game to MCP-compatible AI clients.2MIT
- AlicenseAqualityCmaintenanceProvides verified game rules, official links, and FAQ for the 17-0 NFL roster strategy game to MCP-compatible AI clients.2MIT
- AlicenseAqualityCmaintenanceProvides game rules, roster constraints, FAQ, and official links for the 27-0 NRL fantasy draft game, enabling AI clients to retrieve this knowledge.2MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Rocniubi/27-0-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server