Famly (BYOK)

Famly (BYOK) — connector documentation

• MCP endpoint: https://byok-famly.connectorbay.com/mcp
• REST API: POST https://byok-famly.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-famly.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Famly Famly API access token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-famly.connectorbay.com/health · Tool schemas: https://byok-famly.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-famly · agent@connectorbay.com

What Famly (BYOK) is for

Famly (BYOK) lets an AI assistant read your own Famly data through the Famly API with a key you supply (Famly API access token). Read-only: 8 tools (list_sites, list_groups, list_invoices, list_meal_plans, list_work_tags, list_absence_subtypes, list_roles, list_registration_forms). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to famlyapi.famly.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Famly. Famly and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which sites does my Famly account cover?"
• "What rooms or groups do we have at our nursery?"
• "What invoices did my Famly site issue in October?"
• "What meals are planned at my Famly site this week?"
• "What work tags are defined for our staff shifts?"
• "What kinds of staff absence can we record?"

What it does

• list_sites: List the centre's sites (settings) with id, title, description, email and address. Child and staff data are not requested.
• list_groups: List rooms (groups) the token can access, with title, description, staff ratio, order and the site set they belong to.
• list_invoices: List invoice headers for a site and invoice-date range: number, title, total, invoice date and due date. No lines or child ids are requested. Paged with a cursor.
• list_meal_plans: List planned meals per day for a site (meal type and item titles), by default the current and coming week. Images and files are not requested.
• list_work_tags: List the shift work tags (name, colour, code) defined for a site set.
• list_absence_subtypes: List the staff absence sub-types (leave type, name, code, paid flag) configured for a site set.
• list_roles: List permission roles (title, whether locked, source, target, site sets) the token can see; no role assignees are requested.
• list_registration_forms: List custom registration forms of a site set (name, type, published and shared flags, last edit). Responses and personal data are not requested.

BYOK key

You bring your own Famly Famly API access token (https://docs.famly.co/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to famlyapi.famly.co over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Notices

Centre administration data only: children, parents, contacts, staff personal records, attendance and health data are not requested. Read-only GraphQL queries.

Data sources

• https://docs.famly.co/ (the API this connector calls, with a BYOK key)

Live from the Famly API (famlyapi.famly.co) with a BYOK key; documentation: https://docs.famly.co/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Famly. Famly and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Famly account.

Built for: Worldwide. Languages: English.

Famly (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Famly (BYOK) is. Famly (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Famly data: Read your childcare centre's sites, rooms, invoice totals, meal plans, staff roles and registration forms from Famly with your own access token. You bring your own Famly Famly API access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Famly call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to famlyapi.famly.co, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Famly rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Famly receives. The request we make on your behalf, including the key and the arguments, under Famly's own terms and privacy policy. Famly acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Famly gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Famly data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Famly (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Famly at any time to end all access.

Children. Famly (BYOK) is a general-audience service operated by the adult using the assistant, under Famly's own age rules.

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

Famly (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Famly (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Famly (BYOK) provides: Read your childcare centre's sites, rooms, invoice totals, meal plans, staff roles and registration forms from Famly with your own access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Famly credentials and only access data you are allowed to access. Famly's terms apply to your use of Famly; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Famly. Famly and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Famly returns, lightly trimmed; it may be incomplete, delayed or changed by Famly. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Famly account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Famly's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Famly may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Famly key.
10. 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, including any action Famly takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-famly

Famly (BYOK) support

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

• MCP endpoint: https://byok-famly.connectorbay.com/mcp
• REST API: https://byok-famly.connectorbay.com/openapi.json
• Live status: https://byok-famly.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. Famly (BYOK) never asks for them.