Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Quest Game icon

Quest Game

A hand-curated genre reference for adventure/quest narrative tabletop games — mechanics, structures, and real examples

Unify Dynamics LLC

Documentation
Tools8read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What is codeword gating in a gamebook?
Tools called
mechanic_info
What's a hub-and-spoke narrative structure?
Tools called
narrative_structure_type
What does MacGuffin mean in a game?
Tools called
term_glossary
What games use a legacy campaign mechanic?
Tools called
game_examples
How do designers manage branching complexity?
Tools called
design_consideration
What's a good quest game for 4 players?
Tools called
find_game_for_group
What mechanic categories do you cover?
Tools called
category_list
Give me some tips for my first branching adventure game
Tools called
beginner_tips

About

Questgame is a fully local, hand-curated genre reference for adventure/quest narrative tabletop games — choose-your-path and gamebook mechanics, branching narrative structures, exploration-and-discovery systems, and quest-log/objective-tracking design — not a rules database for any single trademarked product. mechanic_info gives one mechanic's full detail: category, how it works, and real games that use it. narrative_structure_type explains one of the four narrative structure types (linear, branching, hub-and-spoke, sandbox) with trade-offs and examples. term_glossary defines genre terms like gamebook, codeword, MacGuffin and convergence point. game_examples lists real published games that use a named mechanic. design_consideration is an in-depth look at a recurring design topic, like managing branching complexity or building replayability. find_game_for_group suggests real games that fit a stated player count. category_list shows every mechanic category with its count. beginner_tips gives original tips for someone new to the genre. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Original, hand-curated genre reference on adventure/quest narrative game mechanics as of build date; real published games referenced factually as examples only; fully local, zero upstream calls

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Look Up a Mechanic or Term4 tools
  • Mechanic infoFull detail for one adventure/quest game mechanic: its category, a plain-language summary, how it works and why designers use it, and real…
  • Narrative structure typeExplains one of the four narrative structure types used to organize an adventure/quest game's story: linear, branching, hub-and-spoke, or sandbox…
  • Term glossaryDefinitions of common adventure/quest game genre terms — gamebook, paragraph, codeword, node, convergence point, MacGuffin, quest log, legacy…
  • Category listEvery mechanic category this reference covers, with how many mechanics are in each.
Design & Recommendations3 tools
  • Design considerationAn in-depth look at one recurring design consideration in adventure/quest narrative games — what the trade-off is, and practical tips for a group…
  • Game examplesReal, published adventure/quest games that use a named mechanic, referenced factually as examples (not a rules database for any one of them).
  • Find game for groupReal published adventure/quest games whose stated player-count range fits a group of this size, best (tightest-range) fits first.
Getting Started1 tools
  • Beginner tipsOriginal tips for someone new to adventure/quest narrative tabletop games — how to track a quest log, handle branching failure, and more.

Information

PublisherUnify Dynamics LLC
CategoryGames & entertainment · Reference
LanguagesEnglish
Built forGlobal
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://questgame.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Word Guess

A real, playable 5-letter word-guessing game with correct per-letter feedback and duplicate-letter handling

Live · MCP + REST6 tools

TQ Engine

A real, playable Twenty Questions game over an original 150-item knowledge bank with real information-gain questioning

Live · MCP + REST10 tools

Tic-Tac-Toe

A real, playable tic-tac-toe game with a genuinely unbeatable minimax AI opponent

Live · MCP + REST5 tools

Syllable Build

A real build-a-word game — unscramble syllable fragments into a curated real word, with hints and scoring

Live · MCP + REST5 tools

RPS Arena

A playable Rock-Paper-Scissors arena with a real pattern-adaptive AI opponent

Live · MCP + REST6 tools

Rhyme Duel

A real rhyming game — genuine rhymes validated by ending SOUND, not spelling, including classic tricky cases

Live · MCP + REST6 tools

Documentation

Back to top

Questgame — connector documentation

  • MCP endpoint: https://questgame.connectorbay.com/mcp
  • REST API: POST https://questgame.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://questgame.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
  • Health: https://questgame.connectorbay.com/health · Tool schemas: https://questgame.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/questgame · agent@connectorbay.com

What Questgame is for

A hand-curated genre reference for adventure/quest narrative tabletop games — mechanics, structures, and real examples.

What it does

Questgame is a fully local, hand-curated genre reference for adventure/quest narrative tabletop games — choose-your-path and gamebook mechanics, branching narrative structures, exploration-and-discovery systems, and quest-log/objective-tracking design — not a rules database for any single trademarked product. mechanic_info gives one mechanic's full detail: category, how it works, and real games that use it. narrative_structure_type explains one of the four narrative structure types (linear, branching, hub-and-spoke, sandbox) with trade-offs and examples. term_glossary defines genre terms like gamebook, codeword, MacGuffin and convergence point. game_examples lists real published games that use a named mechanic. design_consideration is an in-depth look at a recurring design topic, like managing branching complexity or building replayability. find_game_for_group suggests real games that fit a stated player count. category_list shows every mechanic category with its count. beginner_tips gives original tips for someone new to the genre. Keyless; fully local; zero upstream calls; nothing stored.

What it is not

Not an official product of, or affiliated with, any brand, league, publisher, or organization it may factually mention. Questgame is a hand-curated reference and design tool, not a substitute for an official rulebook, certified instruction, or professional advice. Fully local, zero upstream calls, nothing stored.

Tools

Look Up a Mechanic or Term

mechanic_info — Full detail for one adventure/quest game mechanic: its category, a plain-language summary, how it works and why designers use it, and real published games that use it. Use for "what is codeword gating", "how does fog-of-war exploration work". Args: name.

narrative_structure_type — Explains one of the four narrative structure types used to organize an adventure/quest game's story: linear, branching, hub-and-spoke, or sandbox — with a detailed explanation, pros, cons, and real examples. Use for "what's a hub-and-spoke structure", "linear vs branching, what's the difference". Args: name.

term_glossary — Definitions of common adventure/quest game genre terms — gamebook, paragraph, codeword, node, convergence point, MacGuffin, quest log, legacy game, red herring, agency, and more. Use for "what does MacGuffin mean", "what's a convergence point". Args: term.

category_list — Every mechanic category this reference covers, with how many mechanics are in each. Use for "what categories of quest-game mechanics do you cover".

Design & Recommendations

design_consideration — An in-depth look at one recurring design consideration in adventure/quest narrative games — what the trade-off is, and practical tips for a group or designer. Use for "how do designers manage branching complexity", "what makes a quest game replayable". Args: topic.

game_examples — Real, published adventure/quest games that use a named mechanic, referenced factually as examples (not a rules database for any one of them). Use for "what games use a legacy campaign system", "which games have branching dialogue". Args: mechanic.

find_game_for_group — Real published adventure/quest games whose stated player-count range fits a group of this size, best (tightest-range) fits first. Use for "what's a good quest game for 4 players", "any of these playable solo". Args: player_count.

Getting Started

beginner_tips — Original tips for someone new to adventure/quest narrative tabletop games — how to track a quest log, handle branching failure, and more. Use for "tips for my first branching adventure game", "advice for running a quest-log campaign". Args: count.

Conventions

  • Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
  • Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
  • Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/questgame/support

Privacy policy

Back to top

Questgame — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Questgame is. Questgame is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated genre reference for adventure/quest narrative tabletop games — mechanics, structures, and real examples. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call, the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from a bundled, hand-curated reference file and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Questgame is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Questgame — Terms of Service

Effective 25 September 2026. These terms govern use of the Questgame connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Questgame is a fully local, hand-curated genre reference for adventure/quest narrative tabletop games — choose-your-path and gamebook mechanics, branching narrative structures, exploration-and-discovery systems, and quest-log/objective-tracking design — not a rules database for any single trademarked product.
  2. A reference, not professional advice. Questgame is an independent reference and hobby/game-design tool, not affiliated with or endorsed by any brand, organization, league, or publisher it may factually mention. It does not provide legal, financial, medical, or safety-certification advice, and is not a substitute for supervised instruction where real physical risk is involved.
  3. Content varies. Rules, terminology and conventions described here reflect commonly-cited general practice; local house rules, regional variants, and official governing-body rulebooks may differ.
  4. Acceptable use. Automated use within the published rate limits is welcome.
  5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  6. Data. Our Privacy Policy describes what we process. In short: your query is answered from a bundled reference file, and nothing is stored.
  7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service. Our total liability is limited to US $100.
  9. Governing law. California law; venue in San Mateo County, California.
  10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/questgame

Support

Back to top

Quest Game support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Quest Game never asks for them.

Get Quest Game

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://questgame.connectorbay.com/mcp
{
  "mcpServers": {
    "questgame": {
      "type": "http",
      "url": "https://questgame.connectorbay.com/mcp"
    }
  }
}