Micro blog (BYOK)

Micro blog (BYOK) — connector documentation

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

What Micro blog (BYOK) is for

Micro blog (BYOK) lets an AI assistant read your own Micro blog data through the Micro blog API with a key you supply (app token). Read-only: 11 tools (get_timeline, get_mentions, get_bookmarks, get_photo_timeline, get_media_timeline, get_discover, get_discover_collection, get_user_posts, get_conversation, get_my_replies, list_following). 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 micro.blog. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Micro blog. Micro blog 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:

• "What is new on my Micro.blog timeline?"
• "Who mentioned me on Micro.blog?"
• "Which Micro.blog posts have I bookmarked?"
• "Show recent photos on my Micro.blog timeline"
• "Show recent photos and videos on my Micro.blog timeline"
• "What are the featured posts on Micro.blog right now?"

What it does

• get_timeline: List posts in your Micro.blog timeline (people you follow), newest first, with author, text (HTML) and date.
• get_mentions: List posts that mention you, newest first.
• get_bookmarks: List posts you bookmarked on Micro.blog.
• get_photo_timeline: List posts with photos in your timeline, newest first.
• get_media_timeline: List posts with photos or videos in your timeline, newest first.
• get_discover: List featured posts from Micro.blog's Discover page.
• get_discover_collection: List featured posts in one emoji collection of Discover, for example books or music.
• get_user_posts: List posts written by one Micro.blog user, newest first.
• get_conversation: Show the thread around a post: the post and its replies.
• get_my_replies: List replies you posted, newest first.
• list_following: List the users that a given user follows.

BYOK key

You bring your own Micro blog app token (https://micro.blog/account/apps). 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 micro.blog 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://help.micro.blog/t/json-api/97 (the API this connector calls, with a BYOK key)

Live from the Micro blog API (micro.blog) with a BYOK key; documentation: https://help.micro.blog/t/json-api/97. 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 Micro blog. Micro blog 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 Micro blog account.

Built for: Worldwide. Languages: English.

Micro blog (BYOK) — Privacy Policy

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

What Micro blog (BYOK) is. Micro blog (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Micro blog data: Read your Micro.blog timeline, mentions, bookmarks, replies and any user's posts with your own app token. You bring your own Micro blog app token; the assistant sends it to us with each request.

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

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

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

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

Micro blog (BYOK) — Terms of Service

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

1. The Service. Micro blog (BYOK) provides: Read your Micro.blog timeline, mentions, bookmarks, replies and any user's posts with your own app 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 Micro blog credentials and only access data you are allowed to access. Micro blog's terms apply to your use of Micro blog; 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 Micro blog. Micro blog 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 Micro blog returns, lightly trimmed; it may be incomplete, delayed or changed by Micro blog. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Micro blog 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 Micro blog'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; Micro blog 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 Micro blog 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 Micro blog 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-microblog

Micro blog (BYOK) support

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

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