Connectors
Connect a service for your organization from your Profile, from Connected Services in a workspace’s Settings, or on the connectors page (/settings/connectors).
GitLab, Jira, and Miro appear on the connectors page but can’t be connected yet. Each one shows the reason it isn’t available.
Using a connector takes three steps:
- Connect the service once for your organization.
- Link items, such as a repository, an epic, or a design file, to a workspace or outcome.
- Kana reads the linked items as context when she plans and builds.
A connector that signs in with OAuth also needs that sign-in set up in your Kanaeru environment. If it isn’t, the connector shows “This connector is not configured for this Kana environment.”
Context sources
A context source is a linked item that sessions read. Sources attach at three scopes, and narrower scopes inherit from broader ones:- Workspace: every outcome and session in the workspace can use it.
- Outcome: only that outcome’s sessions use it.
- This session: only one session uses it.
Runtime MCP servers
You can also give your agent runtimes extra tools. Under Runtime MCP servers, add a remote MCP server once for your account and choose which runtimes receive it. Official presets are available, and OAuth-based servers are authorized inside Kanaeru.From the terminal
kana connectors and kana context-sources.