Kanka (BYOK)

Kanka (BYOK) — connector documentation

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

What Kanka (BYOK) is for

Kanka (BYOK) lets an AI assistant read your own Kanka data through the Kanka API with a key you supply (Kanka personal access token). Read-only: 12 tools (get_profile, list_campaigns, search_campaign, list_characters, get_character, list_locations, get_location, list_organisations, list_notes, list_quests, list_journals, list_items). 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.kanka.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Kanka. Kanka 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 Kanka account is my token connected to and what is my rate limit?"
• "Which Kanka campaigns do I have?"
• "Find everything called 'Mordor' in my Kanka campaign"
• "Who are the characters in my Kanka campaign?"
• "Show the character with id 1 in campaign 12345"
• "What locations exist in my Kanka campaign?"

What it does

• get_profile: Show the Kanka account the token belongs to: name, locale, timezone, subscriber status and the current request rate limit.
• list_campaigns: List the Kanka campaigns the token owner can access, with name, locale, visibility and dates.
• search_campaign: Search all entities of a campaign (characters, locations, notes, quests and so on) by a word or name.
• list_characters: List a campaign's characters with title, age, sex, races and families (descriptions are left out; use get_character for one).
• get_character: Get one character of a campaign including the full HTML description and basic traits.
• list_locations: List a campaign's locations with title and type (descriptions are left out; use get_location for one).
• get_location: Get one location of a campaign including the full HTML description.
• list_organisations: List a campaign's organisations with type, status and the locations they are linked to.
• list_notes: List a campaign's notes with type and whether they are pinned (text is left out).
• list_quests: List a campaign's quests with type, date and status.
• list_journals: List a campaign's journals (session logs) with type, date and author.
• list_items: List a campaign's items (objects) with type, price, size, weight and the location they are in.

BYOK key

You bring your own Kanka Kanka personal access token (https://app.kanka.io/settings/api). 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.kanka.io 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

Kanka limits each user to 30 requests per minute (90 for subscribers). Results follow the token owner's campaign permissions.

Data sources

• https://app.kanka.io/api-docs/1.0/setup (the API this connector calls, with a BYOK key)

Live from the Kanka API (api.kanka.io) with a BYOK key; documentation: https://app.kanka.io/api-docs/1.0/setup. 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 Kanka. Kanka 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 Kanka account.

Built for: Worldwide. Languages: English.

Kanka (BYOK) — Privacy Policy

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

What Kanka (BYOK) is. Kanka (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Kanka data: Read your Kanka worldbuilding campaigns: characters, locations, organisations, notes, quests, journals and items with your own personal access token. You bring your own Kanka Kanka personal access token; the assistant sends it to us with each request.

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

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

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

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

Kanka (BYOK) — Terms of Service

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

1. The Service. Kanka (BYOK) provides: Read your Kanka worldbuilding campaigns: characters, locations, organisations, notes, quests, journals and items with your own personal 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 Kanka credentials and only access data you are allowed to access. Kanka's terms apply to your use of Kanka; 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 Kanka. Kanka 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 Kanka returns, lightly trimmed; it may be incomplete, delayed or changed by Kanka. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Kanka 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 Kanka'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; Kanka 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 Kanka 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 Kanka 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-kanka

Kanka (BYOK) support

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

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