Miro (BYOK)

Miro (BYOK) — connector documentation

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

What Miro (BYOK) is for

Miro (BYOK) lets an AI assistant read your own Miro data through the Miro API with a key you supply (Miro access token). Read-only: 9 tools (get_token_context, list_boards, get_board, list_board_items, get_board_item, list_board_members, list_board_tags, list_board_connectors, list_board_groups). 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.miro.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Miro. Miro 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 Miro user and team is my token for, and what scopes does it have?"
• "Which Miro boards do I have?"
• "Show the details and sharing settings of this Miro board"
• "What sticky notes are on this Miro board?"
• "Show this item on my Miro board"
• "Who has access to this Miro board?"

What it does

• get_token_context: Show what the Miro access token belongs to: user, team, organization and granted scopes.
• list_boards: List Miro boards the token's user can access, optionally filtered by team, project (space), owner or a name search.
• get_board: Get one Miro board: name, description, owner, team, sharing access and view link.
• list_board_items: List items on a Miro board (sticky notes, text, shapes, cards, frames, images, embeds) with their text and position. Cursor paging.
• get_board_item: Get one item from a Miro board by item ID, with its text content, position and timestamps.
• list_board_members: List the members of a Miro board with their role (viewer, commenter, editor, coowner or owner).
• list_board_tags: List the tags defined on a Miro board with title and color.
• list_board_connectors: List the connectors (lines and arrows between items) on a Miro board with their shape and the item IDs they join.
• list_board_groups: List the groups on a Miro board with the IDs of the items in each group.

BYOK key

You bring your own Miro Miro access token (https://developers.miro.com/docs/rest-api-build-your-first-hello-world-app). 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.miro.com 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.

Data sources

• https://developers.miro.com/reference/get-boards-1 (the API this connector calls, with a BYOK key)

Live from the Miro API (api.miro.com) with a BYOK key; documentation: https://developers.miro.com/reference/get-boards-1. 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 Miro. Miro 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 Miro account.

Built for: Worldwide. Languages: English.

Miro (BYOK) — Privacy Policy

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

What Miro (BYOK) is. Miro (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Miro data: Read your Miro boards, board items, tags, connectors, groups and members with your own access token. You bring your own Miro Miro access token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Miro 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.miro.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Miro 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 Miro receives. The request we make on your behalf, including the key and the arguments, under Miro's own terms and privacy policy. Miro acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Miro 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 Miro 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. Miro (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 Miro at any time to end all access.

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

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

Miro (BYOK) — Terms of Service

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

1. The Service. Miro (BYOK) provides: Read your Miro boards, board items, tags, connectors, groups and members 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 Miro credentials and only access data you are allowed to access. Miro's terms apply to your use of Miro; 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 Miro. Miro 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 Miro returns, lightly trimmed; it may be incomplete, delayed or changed by Miro. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Miro 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 Miro'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; Miro 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 Miro 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 Miro 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-miro

Miro (BYOK) support

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

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