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

Ludo

A hand-curated cross-and-circle race-game reference — Pachisi, Ludo, Parcheesi, Sorry! and more

Unify Dynamics LLC

Tools9read-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 games do you cover?
Tools called
game_list
How do you capture a piece in Ludo?
Tools called
rule_lookup
What does 'blockade' mean?
Tools called
term_glossary
What's the three-sixes-forfeit rule?
Tools called
variant_info
What's the difference between Ludo and Parcheesi?
Tools called
game_comparison
How do you set up Aggravation for 6 players?
Tools called
player_count_setup
Any strategy tips for Parcheesi?
Tools called
strategy_concept
Beginner tips for playing Ludo?
Tools called
beginner_tips
Where does Ludo come from?
Tools called
history_note

About

Ludo is a fully local, hand-curated, original-content reference for cross-and-circle race games. game_list gives a quick-reference table of all six games covered with origin, players, randomizer and signature twist. rule_lookup gives one game's rule for a topic — starting, movement, capturing, safe squares, blocking, extra turns, home stretch, winning, team play — or every rule for that game. term_glossary defines shared family terms like yard, home stretch, safe square, blockade, exact count, cowrie shells, Pop-O-Matic, slide and split. variant_info covers named regional and edition variants: two-player Ludo, the three-sixes-forfeit house rule, strict-blockade Parcheesi, classic versus Slides-era Sorry!, Frustration, Wahoo/Aggravation regional differences, and the German cousin Mensch ärgere Dich nicht. game_comparison lines up two named games side by side across origin, board, randomizer and key rules. player_count_setup gives seating and rule adjustments for a game at a specific player count, from 2 up to Aggravation's 6-player star board. strategy_concept explains a named tactical idea for a game plus cross-family concepts like capturing-over-racing. beginner_tips gives an ordered starter shortlist for a game. history_note gives a game's origin region and a hedged historical note, since this family is old and was passed down informally for a long time. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Original, hand-written descriptions of widely known cross-and-circle race-game mechanics, with hedged, qualitative historical dating where exact dates are genuinely debated; 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.

What it can do

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

OpenAPI
Look Up a Game4 tools
  • Game listA quick-reference table of every game covered: id, family role (ancestor/adaptation/descendant), origin region, player count, randomizer…
  • Rule lookupOne game's rule for a specific topic (starting, movement, capturing, safe_squares, blocking, extra_turns, home_stretch, winning, team_play,…
  • Term glossaryDefinitions of shared cross-and-circle family terms — yard/base, home column, safe square, capture, block/blockade, exact count, cowrie shells,…
  • Variant infoDetails on a named regional or edition variant (two-player Ludo, the three-sixes-forfeit house rule, mobile-app Ludo conventions, Mensch ärgere…
Compare & Set Up2 tools
  • Game comparisonSide-by-side comparison of two named games across origin, board shape, randomizer, pieces, signature twist, and their…
  • Player count setupSeating/setup guidance and rule adjustments for playing a specific game at a specific player count — which yards to use, what to do with unused…
Play Better2 tools
  • Strategy conceptA named tactical concept for a game (timing your exit, stacking for safety, building a blockade, holding the Sorry!
  • Beginner tipsA curated shortlist of starter tips for learning a game, ordered from most to least essential.
Background1 tools
  • History noteOne game's origin region, family role (ancestor/British adaptation/American adaptation/descendant), and a hedged historical note — this family is…

Information

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

More like this

Platform Mini

A real, playable platformer with genuine gravity, collision, and provably-solvable levels

Live · MCP + REST3 tools

Tower Defense

A real, playable tower-defense engine with genuine range, damage, and gold math

Live · MCP + REST4 tools

Breakout Sim

A real, playable brick-breaker with tick-by-tick physics and angle-reflection bounces

Live · MCP + REST4 tools

Pong Score

A real, playable paddle-and-ball game with tick-by-tick physics and a bounded AI

Live · MCP + REST4 tools

Snake Logic

A real, playable snake game with genuine collision, growth, and food-spawn logic

Live · MCP + REST3 tools

Categories Game

A real, playable Categories/Scattergories-style game session with genuine scoring

Live · MCP + REST6 tools

Documentation

Back to top

Ludo — connector documentation

  • MCP endpoint: https://ludo.connectorbay.com/mcp
  • REST API: POST https://ludo.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://ludo.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://ludo.connectorbay.com/health · Tool schemas: https://ludo.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/ludo · agent@connectorbay.com

What Ludo is for

A hand-curated cross-and-circle race-game reference — Pachisi, Ludo, Parcheesi, Sorry! and more.

What it does

Ludo is a fully local, hand-curated, original-content reference for cross-and-circle race games. game_list gives a quick-reference table of all six games covered with origin, players, randomizer and signature twist. rule_lookup gives one game's rule for a topic — starting, movement, capturing, safe squares, blocking, extra turns, home stretch, winning, team play — or every rule for that game. term_glossary defines shared family terms like yard, home stretch, safe square, blockade, exact count, cowrie shells, Pop-O-Matic, slide and split. variant_info covers named regional and edition variants: two-player Ludo, the three-sixes-forfeit house rule, strict-blockade Parcheesi, classic versus Slides-era Sorry!, Frustration, Wahoo/Aggravation regional differences, and the German cousin Mensch ärgere Dich nicht. game_comparison lines up two named games side by side across origin, board, randomizer and key rules. player_count_setup gives seating and rule adjustments for a game at a specific player count, from 2 up to Aggravation's 6-player star board. strategy_concept explains a named tactical idea for a game plus cross-family concepts like capturing-over-racing. beginner_tips gives an ordered starter shortlist for a game. history_note gives a game's origin region and a hedged historical note, since this family is old and was passed down informally for a long time. 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. Ludo 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 Game

game_list — A quick-reference table of every game covered: id, family role (ancestor/adaptation/descendant), origin region, player count, randomizer (dice/cowries/cards/Pop-O-Matic), and its one signature twist. Use for "what games do you cover", "what's the difference between all of these at a glance".

rule_lookup — One game's rule for a specific topic (starting, movement, capturing, safe_squares, blocking, extra_turns, home_stretch, winning, team_play, special_squares, signature_move — not every topic applies to every game), or every rule recorded for that game if no topic is given. Use for "how do you capture a piece in Ludo", "what's the home stretch rule in Parcheesi", "how do you win at Sorry!". Args: game, topic.

term_glossary — Definitions of shared cross-and-circle family terms — yard/base, home column, safe square, capture, block/blockade, exact count, cowrie shells, Pop-O-Matic, slide, split, doubles, quadrant... Use for "what's a home stretch", "what does blockade mean", "what's a Pop-O-Matic". Args: term.

variant_info — Details on a named regional or edition variant (two-player Ludo, the three-sixes-forfeit house rule, mobile-app Ludo conventions, Mensch ärgere Dich nicht, strict-blockade Parcheesi, classic vs. Slides-era Sorry!, Frustration, Wahoo/Aggravation regional differences...), or every variant recorded for a given game name. Use for "what's the three sixes rule", "how is UK Ludo different", "what's Frustration". Args: name.

Compare & Set Up

game_comparison — Side-by-side comparison of two named games across origin, board shape, randomizer, pieces, signature twist, and their starting/capturing/home-stretch/extra-turn rules where recorded. Use for "Ludo vs Parcheesi", "how is Sorry! different from Ludo", "compare Pachisi and Aggravation". Args: game_a, game_b.

player_count_setup — Seating/setup guidance and rule adjustments for playing a specific game at a specific player count — which yards to use, what to do with unused colors, and whether a partnership variant is common at 4. Use for "how do you set up Ludo for 3 people", "can Aggravation play 6 people", "2-player Parcheesi setup". Args: game, count.

Play Better

strategy_concept — A named tactical concept for a game (timing your exit, stacking for safety, building a blockade, holding the Sorry! card, using the backward move...), plus cross-family concepts like capturing-over-racing and defensive spacing. Omit name to list every concept for the game; omit game (or pass "general") for just the cross-family concepts. Use for "any Ludo strategy tips", "how do blockades help in Parcheesi", "what's defensive spacing". Args: game, name.

beginner_tips — A curated shortlist of starter tips for learning a game, ordered from most to least essential. Use for "beginner tips for Ludo", "how do I get started with Parcheesi". Args: game, count.

Background

history_note — One game's origin region, family role (ancestor/British adaptation/American adaptation/descendant), and a hedged historical note — this family is old and was long passed down informally, so exact dates are debated and given here as commonly-cited ranges. Use for "where does Ludo come from", "is Pachisi older than Ludo", "history of Parcheesi". Args: game.

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/ludo/support

Privacy policy

Back to top

Ludo — Privacy Policy

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

What Ludo is. Ludo is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated cross-and-circle race-game reference — Pachisi, Ludo, Parcheesi, Sorry! and more. 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. Ludo 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

Ludo — Terms of Service

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

  1. The Service. Ludo is a fully local, hand-curated, original-content reference for cross-and-circle race games.
  2. A reference, not professional advice. Ludo 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/ludo

Ludo 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. Ludo never asks for them.

Get Ludo

Free · No sign-in · Read-only

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

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