Cacoo (BYOK)
Read your Cacoo diagrams, folders, sheets, comments and plan limits with your own API key
Read your Lucid (Lucidchart, Lucidspark, Lucidscale) documents, folders, users, teams and account details with your own API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
get_accountget_my_profilelist_usersget_usersearch_documentslist_root_folder_contentsLucid (BYOK) lets an AI assistant read your own Lucid data through the Lucid API with a key you supply (Lucid API key). Read-only: 9 tools (get_account, get_my_profile, list_users, get_user, search_documents, list_root_folder_contents, list_folder_contents, get_folder, list_teams). 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 api.lucid.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lucid. Lucid and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Lucid API (api.lucid.co) with a BYOK key; documentation: https://developer.lucid.co/reference/overview. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
9 tools, grouped by job. Every one is read-only or compute-only.
https://byok-lucid.connectorbay.com/mcpThree ways in, the same 9 tools.
https://byok-lucid.connectorbay.com/mcpPOST https://byok-lucid.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-lucid.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at developer.lucid.co).Lucid (BYOK) lets an AI assistant read your own Lucid data through the Lucid API with a key you supply (Lucid API key). It is a hosted MCP server with 9 tools such as Get account, Get my profile, List users, Get user, Search documents, List root folder contents, published by Unify Dynamics LLC. It is independent and not affiliated with Lucid.
Add the MCP endpoint https://byok-lucid.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-lucid.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-lucid.json.
Yes: this is a bring-your-own-key connector. Create a Lucid API key at https://developer.lucid.co/reference/creating-a-key and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Cacoo diagrams, folders, sheets, comments and plan limits with your own API key
Read your Cal.com availability schedules, profile time settings, conferencing apps and webhook definitions with your own API key (no bookings or attendee data)
Read your Cal.com event types, booking form field definitions and teams with your own API key (no bookings or attendee data)
Read your Cal.com organization setup (teams, team event types, member attributes, roles, routing form definitions, webhooks) with your own API key and organization id
Read your Calendly profile, event types, scheduled meetings, invitees and organization members with BYOK
Read your Calendly availability schedules and rules, event type availability settings, busy windows, event type hosts and group relationships with your own personal access token (no invitee data)
https://byok-lucid.connectorbay.com/mcpPOST https://byok-lucid.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-lucid.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-lucid.connectorbay.com/health · Tool schemas: https://byok-lucid.connectorbay.com/tools.jsonLucid (BYOK) lets an AI assistant read your own Lucid data through the Lucid API with a key you supply (Lucid API key). Read-only: 9 tools (get_account, get_my_profile, list_users, get_user, search_documents, list_root_folder_contents, list_folder_contents, get_folder, list_teams). 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 api.lucid.co. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lucid. Lucid 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:
get_account: Show the Lucid account the key belongs to: account id and name. Needs the AccountReadonly grant.get_my_profile: Show the key owner's Lucid profile: name, username, email and account id. Needs the User grant.list_users: List users on the Lucid account with roles and enabled flag. Needs the AccountAdmin grant (account owner or admin).get_user: Get one Lucid user on the account by numeric user id. Needs the AccountReadonly grant.search_documents: Search Lucid documents the key can see by keywords; returns title, links, product and timestamps. Needs the DocumentReadonly grant.list_root_folder_contents: List the folders and documents in the key owner's root folder (My Documents). Needs the FolderReadonly grant.list_folder_contents: List the folders and documents inside one Lucid folder by id. Needs the FolderReadonly grant.get_folder: Get one Lucid folder: name, type (folder or team), parent, creation and trash dates.list_teams: List Lucid teams the key owner can see with type, creation and archive dates.You bring your own Lucid Lucid API key (https://developer.lucid.co/reference/creating-a-key). 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 api.lucid.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.
Live from the Lucid API (api.lucid.co) with a BYOK key; documentation: https://developer.lucid.co/reference/overview. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Lucid. Lucid 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 Lucid account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Lucid (BYOK) is. Lucid (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Lucid data: Read your Lucid (Lucidchart, Lucidspark, Lucidscale) documents, folders, users, teams and account details with your own API key. You bring your own Lucid Lucid API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Lucid 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 api.lucid.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 Lucid 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 Lucid receives. The request we make on your behalf, including the key and the arguments, under Lucid's own terms and privacy policy. Lucid acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Lucid 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 Lucid 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. Lucid (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 Lucid at any time to end all access.
Children. Lucid (BYOK) is a general-audience service operated by the adult using the assistant, under Lucid's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Lucid (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-lucid.connectorbay.com/mcphttps://byok-lucid.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. Lucid (BYOK) never asks for them.