---
title: Source
order: 2
description: How the agent gets context — tickets, clusters, skills, and more.
---

# Source

A **source** is anything the agent can read inside a workspace. Sources live
in the left panel and are how Investibook builds context.

![Add Source modal binding an Alert ID](/docs/_assets/add-source-modal.png)

## Source types

| Type | What it is | Typical use |
| --- | --- | --- |
| **Jira issue** | An alert / TCOC / TCID case ID | Bind a ticket to pull description, comments, and linked issues. |
| **Cluster meta** | A TiDB Cloud cluster ID | Unlocks Clinic metrics, slow logs, profiles, events. |
| **Git repo** | A repo, commit, or PR link | Code-aware diagnostics. |
| **User meta** | Free-form notes | Provide extra context the agent should know. |
| **Skill** | Display-only capability entry | Surface a built-in skill so the agent knows it can use it. |
| **MCP connector** | An MCP server bound to this workspace | E.g. Clinic, Wait, DevOps. |

## How sources affect the agent

When you ask a question, Investibook looks at the sources and decides which
**MCP tools, resources, or skills** to invoke. The richer your sources, the
less the agent has to guess.

For example: bind a Jira alert, and the agent immediately knows the cluster
ID, alert type, and timeline; it can then call Clinic for metrics, slow
queries, or screenshots without you having to specify them.

## Removing a source

Hover any source and click the trash icon. Removing a source doesn't delete
the underlying ticket or cluster — only the link from this workspace.