Larp

Larp — connector documentation

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

What Larp is for

A hand-curated LARP reference — mechanics, real safety/consent practices, terms and event structures.

What it does

Larp is a fully local, hand-curated live-action role play (LARP) reference. mechanic_info explains a core LARP mechanic — boffer combat, ranged combat, call-based/theater-style combat, hit points, stat & skill systems, dice/card resolution, physical representations, tag/touch systems, marshal adjudication, downtime & logistics. safety_mechanic_info covers a real, community-documented consent/safety mechanic: cut, hold, lookdown, brake, OK-check-OK, tap-out, the X-card, pre-game consent negotiation, debrief & decompression, and the buddy system. term_glossary defines LARP terminology across people & roles, play & fiction, gear & props, and events & structure. event_structure_info explains how an event type is organized, from a single-session one-shot to an ongoing multi-year campaign. combat_safety_note gives real-world physical-safety guidance for boffer/padded-weapon combat topics like weapon construction, strike zones, and grappling restrictions. find_larp_style_for_interest suggests a LARP style that fits a stated interest. category_list lists every browsable category with counts, and beginner_tips gives a curated shortlist of practical advice for a first-time LARPer. 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. Larp 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

How LARPs Work

mechanic_info — Explains one core LARP mechanic: what it is, how it works in practice, and any notes on how it varies between communities. Use for "how does boffer combat work", "what are hit points in larp", "how does downtime work". Args: name.

event_structure_info — Explains how a type of LARP event is organized: typical length, level of commitment, and who it suits best — from a single-session one-shot through an ongoing multi-year campaign. Use for "what's a one-shot larp", "how does an ongoing campaign larp work", "what is a blackbox larp". Args: name.

Safety & Consent

safety_mechanic_info — Explains one real, community-documented LARP safety or consent mechanic: what it is, how it's called and answered, when it's used, and cautions. These are genuine practices used across the LARP community — always confirm the exact convention with a specific event before relying on it. Use for "what is the cut safeword", "how does OK-check-OK work", "what does lookdown mean in larp". Args: name.

combat_safety_note — Real-world physical-safety guidance for a boffer/padded-weapon combat topic: weapon construction & padding, weapon & armor inspection, strike zones, swing control, body armor, eye protection, terrain awareness, heat & hydration, new-combatant orientation, and grappling restrictions. This is general guidance, not a substitute for a specific event's own safety rules. Use for "how should a boffer weapon be built", "what areas are safe to hit in larp combat", "is grappling allowed in larp". Args: topic.

Reference

term_glossary — Defines common LARP terminology — PC, NPC, GM, marshal, plot team, monster camp, bleed, metagaming, powergaming, immersion, garb, phys-rep, boffer, module, chapter, blackbox, parlor larp, Nordic larp, boffer war, and more. Use for "what does bleed mean in larp", "what's the difference between a PC and an NPC", "what is a phys-rep". Args: term.

category_list — Every browsable category across mechanics, safety mechanics, and glossary terms, each tagged with its domain and entry count. Use for "what categories of larp mechanics do you cover", "what glossary categories are there".

Getting Started

find_larp_style_for_interest — Suggests 1-3 LARP styles that fit a stated interest, keyword-matched against each style's tagged interests. Use for "what kind of larp should I try if I like mystery stories", "what larp style fits someone who wants to try it once", "is there a larp style for people who like crafting systems". Args: interest.

beginner_tips — A curated shortlist of practical, plain-language tips for a first-time LARPer — what to bring, what to ask, and how to use safety mechanics. Use for "what should a first-time larper know", "tips for my first larp event". 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/larp/support

Larp — Privacy Policy

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

What Larp is. Larp is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated LARP reference — mechanics, real safety/consent practices, terms and event structures. 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. Larp is a general-audience service operated by the adult using the assistant.

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

Larp — Terms of Service

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

1. The Service. Larp is a fully local, hand-curated live-action role play (LARP) reference.
2. A reference, not professional advice. Larp 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/larp

Larp support

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

• MCP endpoint: https://larp.connectorbay.com/mcp
• REST API: https://larp.connectorbay.com/openapi.json
• Live status: https://larp.connectorbay.com/health

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