> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kanaeru.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors and context

> Bring issues, docs, designs, and conversations into Kanaeru so agents work from the full picture.

Connectors link Kanaeru to the tools your team already uses. Context sources decide which of those items each workspace, outcome, or session reads.

## 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`).

| Service | What it brings in | Live |
| - | - | - |
| GitHub | Repositories, issues, and pull requests. See [GitHub](/guides/github) | Yes |
| Slack | Team discussions (read-only) | Yes |
| Linear | Issues and tickets | Snapshot only |
| Notion | Pages from your knowledge base | Snapshot only |
| Figma | Design files | Snapshot only |
| SharePoint | Documents you can access | Snapshot only |
| Excalidraw | Drawings, linked by URL. No sign-in needed | Snapshot only |

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:

1. **Connect the service** once for your organization.
2. **Link items**, such as a repository, an epic, or a design file, to a workspace or outcome.
3. Kana reads the linked items as **context** when she plans and builds.

Content from connected services is treated as untrusted input. Agents read it as information, not as instructions.

<Note>
  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."
</Note>

## 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.

A source can be **Live**, which keeps it updated as new events arrive, or a one-time snapshot. Live sources are available for GitHub repositories, issues, and pull requests, and for Slack messages. Everything else is a snapshot. You can pause a live source without removing it.

Pull requests are a common live source. While an agent is caring for a pull request, events on it, such as reviews, comments, and CI results, wake that session.

## 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

```bash theme={null}
kana connectors capabilities
kana connectors link <connector-id> --outcome <outcome-id> --type repository --url https://github.com/acme/api
kana context-sources list --outcome <outcome-id>
```

See [`kana connectors`](/cli/reference#kana-connectors) and [`kana context-sources`](/cli/reference#kana-context-sources).


## Related topics

- [Settings and profile](/guides/settings.md)
- [Command reference](/cli/reference.md)
- [Working with Kana](/guides/working-with-kana.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.