Capacities (BYOK) — connector documentation
- MCP endpoint:
https://byok-capacities.connectorbay.com/mcp - REST API:
POST https://byok-capacities.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec athttps://byok-capacities.connectorbay.com/openapi.json - Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
- Authentication: your own Capacities Capacities personal API token (cap-api-...), sent in the
X-Upstream-Keyheader of every request (never stored, logged or cached) - Health:
https://byok-capacities.connectorbay.com/health· Tool schemas:https://byok-capacities.connectorbay.com/tools.json - Publisher: Unify Dynamics LLC · connectorbay.com/byok-capacities · agent@connectorbay.com
What Capacities (BYOK) is for
Capacities (BYOK) lets an AI assistant read your own Capacities data through the Capacities API with a key you supply (Capacities personal API token (cap-api-...)). Read-only: 7 tools (get_space, list_structures, search_objects, list_objects_by_structure, list_objects_by_tag, list_objects_by_collection, get_object). 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.capacities.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Capacities. Capacities 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 Capacities space is my token connected to?"
- "What object types do I have in Capacities?"
- "Find my Capacities notes titled 'project alpha'"
- "List all my Capacities pages"
- "Which Capacities objects have tag 'Reading'?"
- "What is in my Capacities collection 'Books'?"
What it does
get_space: Show the Capacities space the token is bound to (each token has exactly one space): id and title.list_structures: List the object types (structures) of the space: id, name, plural name, label color and collections; ids are used by the listing tools.search_objects: Search objects of the space by title, most relevant first (one page, no cursor).list_objects_by_structure: List summaries (id, type id, title) of objects of one type (structure), 100 per page with cursor paging. Answer has hasMore and nextCursor.list_objects_by_tag: List summaries (id, type id, title) of objects carrying one tag, 100 per page with cursor paging. Answer has hasMore and nextCursor.list_objects_by_collection: List summaries (id, type id, title) of objects in one collection (database), 100 per page with cursor paging. Answer has hasMore and nextCursor.get_object: Get one object by id: its type, collections and property values (title, tags, dates and so on) keyed by property id.
BYOK key
You bring your own Capacities Capacities personal API token (cap-api-...) (https://docs.capacities.io/developer/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.capacities.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.
Data sources
- https://developers.capacities.io/api/overview (the API this connector calls, with a BYOK key)
Live from the Capacities API (api.capacities.io) with a BYOK key; documentation: https://developers.capacities.io/api/overview. 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 Capacities. Capacities 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 Capacities account.
Built for: Worldwide. Languages: English.