Connect your AI
MCP tool reference
The Epic Context connector offers 96 tools, grouped here by what you use them for: orienting and reading, the graph, writing, projects and organisations, skills, the editors and the Epic Suite. Every tool's full description and input schema come with the connection itself.
Your AI client receives every tool with its description and input schema when it connects, so you rarely need this page to call them. Use it to know what exists and which tool fits a job. Most tools take a project_id; on a connection bound to one project it defaults to that project.
Orient and read
| Tool | What it does |
|---|---|
list_projects | The projects you can reach, with their organisation |
get_orientation | A project's binding and state; without a project, your organisations and their shared context |
get_briefing | The briefing for a task: required blocks in full, related excerpts, gaps, the expert and a briefing_id. See Briefings |
get_context_pack | A paste-ready summary of about 4,000 tokens, for a sub-agent or a tool without access |
get_context_for_task | An older, keyword-based briefing; prefer get_briefing |
get_book | The whole project as one markdown document, or one chapter of it |
get_context | The full project context as structured data |
get_project | Project details, its sections and how much is written |
list_blocks | Blocks with filters, inherited organisation blocks included |
get_block | One block by key, name or alias: content, open messages, its url, and its owners where the organisation named them |
search_blocks | Find blocks by name or text; exact name and alias matches first |
list_sections | The sections and the block types each allows |
list_documents | Documents uploaded to the project |
list_design_versions | The workspace's versions of its design system and prototype: each branch, its preview address and its link in Design (read-only) |
get_recent_changes | Recent activity |
get_evidence_for | The evidence the graph holds for a block or an entity |
get_context_card | A block as a card (SVG plus data), to place on a Figma, FigJam or Miro board |
The graph
| Tool | What it does |
|---|---|
list_v3_entities | The eight groups and thirty-four entities, with their blocks |
get_v3_entity | The blocks of one entity, for example persona |
get_v3_overview | How many blocks are stub, assumed, validated or superseded, and the most mature state per entity: the answer to "what is the state of this project?" |
scaffold_v3_project | One stub per entity that is still missing; safe to run again |
check_project_health | A score from 0 to 100, findings (orphans, stubs, broken references) and the writes that fix them |
detect_drift | Broken references and rule violations |
Write
Every write takes a reason, lands directly and shows in the changes feed.
| Tool | What it does |
|---|---|
create_block / update_block | Create or update a block; pass briefing_id for core blocks and expected_version to avoid overwriting someone else. Where the organisation has owners approve changes, update_block on a validated block whose part you do not own answers proposed with its owners: nothing is written until one of them approves |
delete_block | Archive a block: it leaves the book and waits in the project's archive, where anyone who can edit restores it. Erasing it for good is done in the browser, by an owner or admin. See Deleting |
link_blocks | A typed link between two blocks: supports, supersedes, contradicts… See Relations |
unlink_blocks | End a link that is wrong or settled, with a reason; it stays readable with who ended it and why |
lock_block / unlock_block | Make a block read-only for everyone, or open it again (owners and admins) |
share_block | Give a page a public link for someone outside the organisation, or end it; ask the person first. See Sharing one page |
save_rule / log_learning | Keep a rule or a learning under an expert; no briefing needed |
upload_asset | Upload a brand asset (an SVG or an image) to the Design group |
ingest_text | Turn free text (a transcript, an e-mail thread, notes) into writes, as one batch that reverts in one action. A new page and a pure scaffold stub are written; a change to any other existing page is a proposal for whoever holds it (proposed), decided on the page |
extract_from_document | Turn an uploaded document into blocks, each linked to the document and marked assumed |
list_comments / ingest_comments | Read the comments left with the review widget, and run chosen ones into the brain |
Projects and organisations
| Tool | What it does |
|---|---|
create_project | A new project, scaffolded with the thirty-four entities |
create_organization | A new organisation and its org project (not with an API key) |
update_project | Rename a workspace or give it a new address or description, with a reason; old links keep working |
delete_project | Delete a workspace with everything in it; a dry run unless confirmed (owners and admins, never the shared context) |
move_project | Move a project to another organisation; a dry run unless confirmed |
set_project_words | The project's kind of work and its own words for groups and entities |
get_org_context | What the project inherits from its organisation, with the drift report |
override_block | Differ from an organisation block, in this project only, per field, with a reason |
pin_org_block | Read an organisation block at a fixed version, or follow it live again |
move_block_to_org | Move a block to the organisation's org project, with its history (owners and admins) |
ensure_org_project | Create the organisation's org project if it does not exist (owners and admins) |
propose_promotions | Propose to an org block's owner what several projects override the same way (owners and admins) |
get_ownership | Who owns which part of the organisation's brain: every part with its owners and lead, and the parts nobody owns yet. Only where the organisation switched owners on |
propose_owner | Propose a member as an owner or the lead of a part: a card for the organisation's owners and admins. It never assigns anyone; people do |
get_brain_health | Brain health: one score from 0 to 100 for the project, a group or the organisation, with what each part gave (fresh, proven, connected, nothing open) and the blocks behind it. It counts blocks, never people. Only where the organisation switched brain health on |
confirm_block | Record that a block is still true, for its owner who just said so. An event beside the block: its content and version stay as they are, also when it is locked. Refused for anyone who does not own the block |
list_proposals | The changes that wait for an owner in the project, the oldest first: the block, who proposed it and why, what it sets, and the day after which it goes to the part's lead. Where the organisation has owners approve changes; and always the changes an ingest proposed to existing pages |
decide_proposal | Approve or decline a proposed change, for an owner of the block's part who just said so. Approving applies it against the version it was made on; a block that changed since is reported, never overwritten. Refused for anyone who does not own the block's part |
get_brain_check | The brain check's cards for the person you work for: what the brain asks them about the pages they own, the oldest first, each with its evidence and the answers it takes. Only where the organisation has the brain check on. With blind rounds on, also the rounds the person is in: before the reveal only their own answer, after it every owner's answer with names |
answer_brain_check | Answer one card with the answer the person just gave: still true, changed (one line), who is right (with a reason), keep or take a proposal, or not my area. Marked as coming through an AI session; a locked page is never changed, and not my area only teaches the brain whom to ask. With blind rounds on, where other owners of the page were asked the same, the answer waits blind for theirs |
who_knows | Whom to ask about a topic in the organisation: one or two people, with why (the owner or lead of its part, a colleague named them, they said they know it). Never more than two, never a count, never who was not named. Only for a person's own session, where the organisation has Who knows what on |
Skills
| Tool | What it does |
|---|---|
list_skills | The eleven skills, their sub-skills and the organisation's own packs; query searches them |
get_skill | A skill or a file inside it; with project_id, the organisation's and project's expertise under the method |
import_skill | Preview a skill from GitHub or skills.sh: its card, files and checks. Loading it is done in the web, by a person |
propose_skill_delta | Propose a change to a shipped skill, from a project you read (project_id); it goes live only when a platform skill admin, not you, commits it in the web |
list_pending_skill_deltas | The proposals waiting for review (reviewing is done in the web) |
The editors and checks
| Tool | What it does |
|---|---|
get_redactie | The editors' state and what they measured |
run_redactie | Run a round now: structure, content, planner or digest (owners and admins) |
check_citations | Check that every claim in an answer cites a block@version that carries it |
run_question_set | Run a fixed set of questions with known answers against the project's briefings |
get_adoption | The session log: did sessions read a briefing and load their expert before they wrote? |
The Epic Suite
| Tool | What it does |
|---|---|
share_plan | Put the plan of the work on the board: one card, a sub-card per step, kept current |
hand_off | Turn what is left for people into cards for named members |
create_task | One card on one person's board |
notify | Tell one person something they must know but not do |
write_note / list_notes / get_note | Write, find and read notes in Notes |
get_artifact_kit | What an artifact's page can use: the organisation's own colours, typefaces, pictures and motion, and what a page cannot do |
create_artifact | Make an artifact: a plan to send, as one free HTML page in the organisation's own style. Refused without a brief and a storyline |
update_artifact | Publish a new version of an artifact on the same link, with a note on what changed |
get_artifact / list_artifacts | Read an artifact with its story, a version's HTML and its open feedback; list a workspace's artifacts |
list_handoffs | Open cards, notifications and plans; with today: true, your own Today: what waits for you, your part of the brain, how it was used and what got better (where the organisation switched Today on) |
close_handoff | Close a card as done or cancelled, where no board does it (the person it is for, or an owner or admin) |
list_tool_actions / call_tool_action | The actions the organisation's tools offer, and running one with a reason |
list_data_sources | Which data sources the organisation connected (LinkedIn, Microsoft Advertising, and Analytics' sources: Google Analytics, Search Console, Google Ads, Ahrefs, its own measurement), what this project chose to read, and which tool asks each |
query_linkedin / query_microsoft_ads | Ask a signed-in data source a question: figures only, read only, logged with a reason |
get_website_figures | A source's report for a fixed period (Google Analytics, Search Console, Google Ads, Ahrefs or the organisation's own measurement): totals with their change and the main breakdowns, the same figures as the Analytics pages |
query_google_analytics / query_search_console / query_google_ads / query_ahrefs | Ask one of Analytics' sources a specific question, for what was chosen for this project in Organisation › Connections: read only, logged. An Ahrefs question costs API units |
list_recommendations / get_recommendation | What Analytics' recommendation rounds proposed for this workspace and the organisation, newest first and by state (open, approved, approved with a condition, rejected); one in full with its figures, their source and period, the proposed change, the judgement and its link in Analytics. Read only: judging one stays in Analytics |
define_connection | Describe an outside API so the organisation can connect it; the key is added by a person in Settings (owners and admins) |
See Plans, hand-offs and notes for when to use which.
Resources
The book is also offered as MCP resources, for clients that browse resources instead of calling tools:
epiccontext://{projectId}/book
epiccontext://{projectId}/llms.txt
epiccontext://{projectId}/book/{group}/{entity}/{blockKey}
Permissions in short
- A read-only token (an API key without the
writescope) can call every reading tool and none that writes. - A connection bound to one project cannot create projects or organisations, move projects or blocks to the organisation, define connections, import skills, review skill proposals, or read the organisation's ownership map and propose an owner. It still reads who owns a block of its own project.
- Your role in the organisation still applies to every call: a viewer reads, a member writes, owners and admins manage.
Next
Last updated: