Jam

Jam — connector documentation

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

What Jam is for

A hand-curated game jam reference — formats, real events, scope and team tips, and judging basics.

What it does

Jam is a fully local, hand-curated game jam reference. format_info explains one common jam time-box format in depth — 48-hour, 72-hour, week-long, two-week, month-long, and the solo/from-scratch ("compo") vs. team-friendly ("jam") divisions popularized by Ludum Dare — including how it tends to feel and scope guidance suited to it. jam_event_info gives factual, hedged detail on a real jam event: founding, cadence, typical format, theme process, judging style and notable facts. term_glossary defines common jam vocabulary (theme, compo, diversifier, scope creep, core loop, vertical slice, MVP, and more). scope_management_tip and team_formation_tip each give a practical tip by topic, or list every topic. judging_criteria_overview explains the common judging models (peer/community rating, panel-judged, unranked) and the categories jams typically score. find_jam_for_skill_level suggests suitable formats and real events for a stated experience level. beginner_tips gives a ranked shortlist for someone jamming for the first few times. 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. Jam 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

Formats & Events

format_info — Full detail for one common game jam format: typical length, how it tends to feel to jam in, who it suits best, and scope guidance suited to that length. Covers 48/72-hour, week-long, two-week, month-long, and the solo/from-scratch ("compo") vs. team-friendly ("jam") divisions. Use for "what is a 48-hour jam like", "what's the difference between a compo and a jam division". Args: name.

jam_event_info — Factual, hedged detail on one real game jam event: founding, cadence, typical format, theme process, judging style, and notable facts, referenced factually rather than as an official rulebook. Use for "what is Ludum Dare", "how does the Global Game Jam work", "what's js13kGames about". Args: name.

Reference

term_glossary — Definitions of common game jam vocabulary — theme, compo, diversifier, scope creep, core loop, vertical slice, MVP, placeholder art, game feel/juice, postmortem, rating period, timebox, and more. Use for "what's a diversifier", "what does 'compo' mean in game jam terms". Args: term.

judging_criteria_overview — Explains how game jam judging commonly works: the three broad models (peer/community rating, panel/judge-scored, and unranked/participation-first), the categories jams typically score (theme, fun, innovation, aesthetics, mood, technical execution, overall), and the optional "diversifier" concept. Use for "how does game jam judging work", "what categories do jams usually score".

Guidance

scope_management_tip — One practical tip for keeping a time-boxed game project's scope achievable — building the core loop first, keeping a cut list, avoiding multiplayer/procgen traps, setting a feature freeze, and more — or, with no topic, the full list of tip topics. Use for "how do I avoid scope creep in a jam", "when should I stop adding features". Args: topic.

team_formation_tip — One practical tip for forming and running a game jam team — defining roles early, ideal team size, finding teammates on a jam's Discord, matching complementary skills, remote-team coordination, and more — or, with no topic, the full list of tip topics. Use for "how do I find teammates for a game jam", "what's a good jam team size". Args: topic.

Getting Started

find_jam_for_skill_level — Suggests suitable jam formats and real events for a stated experience level (first-timer, beginner, intermediate, advanced), with the reasoning behind the suggestions and level-specific tips. Use for "what game jam should a total beginner try first", "what's a good next jam once I'm comfortable jamming". Args: level.

beginner_tips — A ranked shortlist of general advice for someone jamming for the first few times — scoping small, using familiar tools, playtesting early, submitting something even if incomplete, and more. Use for "give me tips for my first game jam", "what should I know before jamming for the first time". 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/jam/support

Jam — Privacy Policy

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

What Jam is. Jam is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a hand-curated game jam reference — formats, real events, scope and team tips, and judging basics. 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. Jam is a general-audience service operated by the adult using the assistant.

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

Jam — Terms of Service

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

1. The Service. Jam is a fully local, hand-curated game jam reference.
2. A reference, not professional advice. Jam 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/jam

Jam support

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

• MCP endpoint: https://jam.connectorbay.com/mcp
• REST API: https://jam.connectorbay.com/openapi.json
• Live status: https://jam.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. Jam never asks for them.