Supported MCP tools
Review what external AI clients can retrieve, prepare, or write through scoped Prism tools.
The exact tool list can grow over time, but the product boundary should stay stable: Prism is the research system, and external AI clients use scoped tools to retrieve or prepare work.
Workflow
Primary steps
- 1Start with get_prism_workspace_context; use profile=essentials when stable folder IDs are already known.
- 2Use get_agent_context_pack with a task, profile, and token budget, then retrieve precise sources as needed.
- 3Use search_library for titles, chunks, or semantic snippets when exact evidence is needed.
- 4Use preflight tools before saving visualization artifacts, including prepare_chart_table_artifact for raw chart/table data.
- 5Use write tools only when enabled and scoped for the client.
Common read workflows
Start with the canonical workspace context, then call get_agent_context_pack with essentials, standard, or deep profile. It returns a contextRunId, token budget and usage, ranked context blocks, evidence, observations, workspace models, recommended tools, and retrieval trace while retaining legacy context fields.
Use search_library, documents, and file chunks to verify exact evidence; observations and workspace models are contextual guidance, not proof.
When the user supplies raw CSV, TSV, Markdown table, or JSON rows, use prepare_chart_table_artifact to normalize a Prism chart or table payload before validation and saving.
For durable research packets, create or reuse a Library, link companies, configure Prism Email aliases or RSS feeds when requested, save source-backed notes and artifacts, create thesis proposals when needed, then create or update a Library Canvas after reading existing canvas state.
Controlled write workflows
When enabled and authorized, Prism can expose draft creation and revision, marker-based visual insertion, article source attachment, create_artifact, library note/folder creation, RSS setup, Email inbox organization and Library saves, thesis proposals, graph relationship edits, version restore, workflow progress reporting, portfolio context updates, and explicit workspace-memory correction.
memory:write is never granted automatically. remember_workspace_memory requires an authorized folder and explicit durable content; correct_workspace_memory preserves correction provenance; forget_workspace_memory requires a stable memory id and explicit confirmation, purges memory content/embeddings/evidence, invalidates derived models, and retains only a non-content fingerprint for audit.
Folder inbox tools can expose the Prism library email address, read selected message bodies, approve or block senders, and save/import inbox messages and attachments into Knowledge. Prism does not send email through MCP; external newsletter signup or forwarding workflows still require a user-authorized external browser or account flow.
MCP tools should not bypass Prism's review surfaces for publishing or other high-impact actions.