Sources and connectors
Pages are what people and agents write. Sources are what they write from: the files behind the pages, kept with the project so the next session knows where a fact came from and whether it has been folded in yet. Connectors bring three outside tools — Linear, Notion, Slack — into the same MCP tool list, read-only.
Sources
Sources in the nav lists the project's files: type, size, status, and whether it has been ingested. Add sources uploads one or more files (up to 100 MiB each); they are stored in object storage, encrypted with your organisation's key. Every plan meters sources across the organisation — Free includes 10; see Limits and plans.
A source carries a status — uploaded when it lands, then
processing, processed or error as WitWiki handles it — and an
ingested mark, which is yours: it says a person or an agent has read the
file and written what mattered into pages. Set it from the row (Mark as
ingested) or let the agent set it. The Ingest monitor (/ingest) is a
live log of upload and processing events for the project.
What an agent can do with sources
| Tool | Does |
|---|---|
wiki_listSources | List the project's sources with status and size |
wiki_getSource | Read one source's record — filename, type, size, status |
source_upload | Upload a file the agent has (base64) and get its record back |
wiki_markSourceIngested | Say the source's content is now in the wiki, so no session re-processes it |
wiki_deleteSource | Delete a source and its file |
One honest limit: over MCP an agent sees a source's record, not its bytes.
The pattern that works today is the agent uploading what it has just read —
a spec, a transcript, an export — with source_upload, writing the pages,
and marking the source ingested, so the next session can see the file exists
and is done. A file uploaded in the browser is listed to agents but they
cannot open it yet; paste the relevant part into the prompt, or hand them the
file. Tool reference has the parameters.
Connectors
Settings → Connections connects a provider with a token: Linear, Notion or Slack. Granola is listed but not available — it has no public API. The token is encrypted at rest and never shown again; test checks it still works, disconnect removes it.
Once connected, the provider's tools appear in the MCP tool list of every agent connected to the organisation, next to the wiki tools. They are read-only:
| Provider | Tools |
|---|---|
| Linear | linear_search_issues (by text), linear_get_issue (by id), linear_list_teams |
| Notion | notion_search (pages and databases shared with the integration), notion_get_page, notion_query_database |
| Slack | slack_list_channels (public channels), slack_read_channel (recent messages), slack_search_messages (needs a token with search:read) |
A connector answers the question an agent used to have to ask a person —
what is the state of that ticket, what did the channel decide — and the
answer can go straight into a page with wiki_patchPage, with the source
named. Connectors are per organisation, so one token serves every project and
every agent in it.
Related
- Limits and plans — sources per plan.
- Teaching your agent — when to write what it read.
- Tool reference — every source tool in full.