Doorkeeper (BYOK)

Doorkeeper (BYOK) — connector documentation

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

What Doorkeeper (BYOK) is for

Doorkeeper (BYOK) lets an AI assistant read your own Doorkeeper data through the Doorkeeper API with a key you supply (Doorkeeper public API access token (from your profile)). Read-only: 5 tools (list_events, list_community_events, get_event, get_community, check_connection). 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.doorkeeper.jp. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Doorkeeper. Doorkeeper 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 events are happening in Tokyo in November 2026?"
• "What events does Doorkeeper community 24 have coming up?"
• "Show Doorkeeper event 28319"
• "Tell me about Doorkeeper community 24"
• "Does my Doorkeeper token work?"

What it does

• list_events: List featured public events on Doorkeeper (25 per page) with title, start and end time, venue, address, ticket limit, attendee and waitlist counts and event link; filter by keyword, prefecture and dates.
• list_community_events: List the events of one Doorkeeper community (group) with title, times, venue, ticket limit and attendee counts.
• get_event: Get one event by its numeric id: title, times, venue, address, coordinates, ticket limit, attendee and waitlist counts and public link.
• get_community: Get one community (group) profile: name, country, description, member count and public page.
• check_connection: Return the current server time to confirm the access token works.

BYOK key

You bring your own Doorkeeper Doorkeeper public API access token (from your profile) (https://www.doorkeeper.jp/developer/api?locale=en). 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.doorkeeper.jp 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://www.doorkeeper.jp/developer/api?locale=en (the API this connector calls, with a BYOK key)

Live from the Doorkeeper API (api.doorkeeper.jp) with a BYOK key; documentation: https://www.doorkeeper.jp/developer/api?locale=en. 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 Doorkeeper. Doorkeeper 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 Doorkeeper account.

Built for: Worldwide. Languages: English.

Doorkeeper (BYOK) — Privacy Policy

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

What Doorkeeper (BYOK) is. Doorkeeper (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Doorkeeper data: Read public community events, event details and community profiles from Doorkeeper (Japan) with your own API access token. You bring your own Doorkeeper Doorkeeper public API access token (from your profile); the assistant sends it to us with each request.

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

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

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

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

Doorkeeper (BYOK) — Terms of Service

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

1. The Service. Doorkeeper (BYOK) provides: Read public community events, event details and community profiles from Doorkeeper (Japan) with your own API 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 Doorkeeper credentials and only access data you are allowed to access. Doorkeeper's terms apply to your use of Doorkeeper; 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 Doorkeeper. Doorkeeper 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 Doorkeeper returns, lightly trimmed; it may be incomplete, delayed or changed by Doorkeeper. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Doorkeeper 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 Doorkeeper'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; Doorkeeper 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 Doorkeeper 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 Doorkeeper 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-doorkeeper

Doorkeeper (BYOK) support

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

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