Skip to main content
This is the Knowledge plane over MCP: the tools an AI client uses to read the team’s context before acting and to write a clean Note after learning. For setup, authentication, and the OAuth scopes referenced below, see MCP & OAuth. Every read carries a flat trust field (reviewed = Knowledge, the team’s source of truth; proposed / draft = a Note, a hint), so a client can key on trust === "reviewed" directly.

Retrieval and reading

Start with driftless_context_retrieve when you have a task but no slug. Bodies come back brief by default (the durable why, not the full content); fetch one full body with driftless_context_get.
ToolPurposeMain paramsReturns
driftless_context_retrieveRanked, drifted-first context for a task and/or filestask, files, view, limit{ shown, has_more, next_action, results[] }
driftless_context_searchFull-text search, relevance-rankedquery, tags, stale, limittop 5 summaries, has_more
driftless_context_listList topics, drifted-firststatus, stale, tags, limittop 40 summaries
driftless_context_getOne topic by slug (full body)topic, viewthe full topic
driftless_context_get_for_filesMatch topics to file pathsfiles, view, limittop 10, brief
Permission: context:read. Availability: Available.
driftless_context_retrieve task:'harden the webhook handler' files:['src/webhooks/handler.ts']
  → { results: [ { slug, trust, why_matched, confidence } ], has_more }

Writing and editing

ToolPurposeMain paramsNotes
driftless_context_createCreate a topic (defaults to Up for review)title, content, pattern, relsreturns anchor_validation
driftless_note_addCapture a private Note (stays a draft)content, project_id, card_idnever auto-submitted
driftless_context_updateAppend-safe updatetopic, fields, relsreturns anchor_validation
driftless_context_deleteDelete a topic (destructive)topicirreversible
driftless_context_mergeFold a duplicate into a survivorsource, intoarchives the source
driftless_context_sharePublish a public page and/or share with memberstopic, to_web, with_memberssharing, not merging
Permissions: topics:create / topics:write; work:write for merge and share. Availability: Available. Write responses carry anchor_validation (ok / overbroad / zero), which never blocks the write.
{ "topic": "refund-flow", "rels": [ { "to": "billing-flow", "type": "depends_on" } ] }

Graph and health

ToolPurposeMain paramsReturns
driftless_context_relationsA topic’s typed relationstopicincoming + outgoing
driftless_context_graphLocal relation graphtopic, depthnodes + edges
driftless_context_doctorAudit the context layer(none)stale / zombie / orphaned / draft
driftless_context_coverageSource areas with no topic(none)the coverage gaps
driftless_context_eventsRecent activity for a topictopicthe event stream
Permission: context:read. Availability: Available.

Registries: tags and areas

ToolActionsPurpose
driftless_tagslist, create, deleteThe tag registry (per-tag counts; curation)
driftless_areaslist, create, update, deleteThe area registry (the domains topics file under)
Permissions: list is member-level; create / update / delete need work:write. Availability: Available.

Governance

A topic becomes Knowledge only once an owner or admin merges it. An MCP client always proposes; it can merge only with owner/admin authority, and only when the authorizing person explicitly asks.
ToolPurposeMain paramsPermission
driftless_context_proposePut a Note up for review (draft → proposed)topicwork:write
driftless_context_approveMerge into Knowledge (proposed → reviewed)topicowner/admin, only when asked
driftless_context_create_proposalOpen a Suggested edit to existing Knowledgetopic, summary, contentwork:write
driftless_context_proposalsList Notes up for review (the review queue)(none)member
Availability: Available. Automatic merge or auto-approval is Not available: a person always decides.
driftless_context_propose topic:'token-verification'

Permissions

ScopeCovers
context:readRead topics, retrieve, search, list, graph, doctor, coverage, events
topics:createCreate topics
topics:writeUpdate existing topics
work:writeTag/area curation, merge, share, propose, and Suggested edits
context:diffRead topic diff for local changes
Merging into Knowledge additionally requires owner/admin authority, not just a scope.