Recall AI (BYOK)
Read your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Scrum roles, events and artifacts verified against the official Scrum Guide, plus Kanban and general Agile terms
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
term_lookupsearch_termsglossary_by_categoryrole_guideceremony_guideartifact_guidescrum_vs_kanbankanban_practicescadence_calculatorcommon_misconceptionsAgileglossary is a fully local Agile/Scrum/Kanban terms and ceremony guide. Scrum roles, events, artifacts, commitments and values are verified against the official 2020 Scrum Guide (scrumguides.org), not recalled from general memory. term_lookup defines any term with its category; search_terms does keyword search; glossary_by_category browses by category. role_guide explains Product Owner, Scrum Master, and Developers with their accountabilities. ceremony_guide explains Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective with purpose, attendees, and maximum timebox for a one-month Sprint. artifact_guide explains Product Backlog, Sprint Backlog, and Increment with their commitments. cadence_calculator scales those one-month-Sprint maximums proportionally for a Sprint length you give it. kanban_practices explains the six core Kanban Method practices. scrum_vs_kanban compares the two frameworks. common_misconceptions corrects frequent mistaken beliefs, including outdated 2017-Guide terminology and practices commonly assumed official (story points, velocity, burndown charts) that are actually common convention layered on top of Scrum. Keyless; fully local; zero upstream calls at query time; nothing stored.
Sources: Scrum roles/events/artifacts/commitments/values verified against the official 2020 Scrum Guide at scrumguides.org (fetched and checked, not recalled from memory); Kanban core practices drawn from published Kanban Method descriptions; general Agile terms labeled as common industry practice, not official framework requirements; cadence scaling computed locally; fully local, zero upstream calls at query time
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
10 tools, grouped by job. Every one is read-only or compute-only.
https://agileglossary.connectorbay.com/mcpRead your Recall.ai meeting bots, recordings, transcripts metadata, calendars and calendar events with your own API key
Read your Bland AI account balance, call logs with summaries and analysis, voices, inbound numbers, knowledge bases and TTS models with your own API key
Read your Postiz Cloud social media schedule: connected channels, scheduled and published posts, analytics, notifications and media library with your own API key
Read your Smartlead cold email campaigns, leads, sending accounts, warm-up stats, lead lists and overall and daily performance with your own API key
Read your Ayrshare social media post history, post details, comments, user profiles and auto-schedule times with your own API key
Read your Publer workspaces, connected social accounts, scheduled and published posts, labels and post, hashtag and best-time analytics with your own API key
"What does the Scrum Guide actually say about the Scrum Master's role?", "how long is a Daily Scrum?", "what's the difference between Scrum and Kanban?" — a fully local reference that was checked against the official Scrum Guide rather than answered from memory, plus published Kanban Method practices and honest labeling of which "Agile" terms (story points, velocity, burndown charts) are actually common convention, not part of either official framework.
role_guide explains a Scrum role — Product Owner, Scrum Master, Developers — with its accountabilities exactly
as the 2020 Scrum Guide states them. ceremony_guide explains a Scrum event — Sprint, Sprint Planning, Daily
Scrum, Sprint Review, Sprint Retrospective — with its purpose, who attends, and its maximum timebox for a
one-month Sprint. artifact_guide explains a Scrum artifact — Product Backlog, Sprint Backlog, Increment — and
its commitment (Product Goal, Sprint Goal, Definition of Done respectively). cadence_calculator scales those
one-month-Sprint maximums proportionally for whatever Sprint length you actually use, since the Guide only states
exact numbers for a one-month Sprint.
term_lookup defines any single term from anywhere in the reference with its category. search_terms does a
keyword search across everything. glossary_by_category browses by category. kanban_practices explains the six
core Kanban Method practices — visualize the workflow, limit WIP, manage flow, make policies explicit, implement
feedback loops, improve collaboratively. scrum_vs_kanban compares the two frameworks on cadence, roles, WIP
limits, and how each handles new work arriving mid-iteration. common_misconceptions corrects frequent mistaken
beliefs — including that "Development Team" (2017-Guide language) is still the current term, and that story
points, velocity, and burndown charts are official parts of Scrum rather than common practices layered on top.
cadence_calculator's scaling math is computed locally. The Scrum roles, events, artifacts, commitments, values,
and pillars were fetched from the official 2020 Scrum Guide at scrumguides.org and checked against that source
directly, not recalled from training-data memory, before being reference-formatted here. Kanban core practices
are drawn from published descriptions of the Kanban Method. General Agile terms (story points, MVP, planning
poker, velocity, burndown charts, and similar) are explicitly labeled as common industry practice rather than
requirements of either official framework, since conflating the two is one of the most common sources of
confusion in this space.
Scrum content reflects the 2020 Scrum Guide specifically — the Guide has been revised before (most notably 2017 to 2020, which is where the "Development Team" terminology changed) and could be revised again, so always check scrumguides.org directly for the current official text. This is a terminology and structure reference, not a certification prep course or a substitute for actually running the framework with a team.
Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Agileglossary is. Agileglossary is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local Agile/Scrum/Kanban terms and ceremony guide, with Scrum content checked against the official 2020 Scrum Guide — roles, events, artifacts, commitments, Kanban core practices, a Scrum-vs-Kanban comparison, and a Sprint-length cadence calculator. You interact with your assistant; the assistant sends us only the text or values needed for that one response.
What we receive. the arguments of each tool call — a term, role, event, artifact, or practice name to look up, a search keyword, or a Sprint length to scale timeboxes for, 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 locally and nothing is stored. Term, role, event, artifact and practice content is answered from a bundled reference file that was checked against the official 2020 Scrum Guide and published Kanban Method descriptions; only the cadence-calculator's proportional scaling is computed from the number you send us — there is no upstream call at all; no request is forwarded to any third party, 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, your name, contacts, or account credentials, and we do not build a profile from your queries — each request is answered independently and nothing carries over between requests. Lookup terms are the only input this connector needs, and we do not build any profile of what you've looked up over time.
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 — every tool is computed or answered locally. Hosting: Vercel (United States regions).
Legal bases and your rights. For users in California, the EU/UK and elsewhere, 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. Agileglossary is a general-audience terminology and process reference operated by the adult using the assistant.
Changes. We will post changes here with a new effective date.
Effective 25 September 2026. These terms govern use of the Agileglossary connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://agileglossary.connectorbay.com/mcphttps://agileglossary.connectorbay.com/openapi.jsonWhen 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. Agile Glossary never asks for them.