MCP Tools

The Marcora MCP Server exposes a set of tools that your AI assistant can call directly to interact with your workspace. Each tool maps to a specific action — from generating content to retrieving context — and can be invoked naturally through conversation.

The tools below are available to any connected AI assistant once the Marcora MCP Server is configured.

Tools

Content

ask_content_assistant

Send a natural-language request to Marcora's in-document Content Assistant to edit, extend, or ideate on an existing document. It runs asynchronously and streams its reply and any edits into the document's sidebar in Marcora.

create_content

Create a content document from an AI prompt, your own supplied text, or a blueprint template. It automatically pulls in all relevant brand and reference context, so there is no need to fetch context first. When generating from `instructions`, you can also pass `reference_content_ids` to fold specific existing documents into the prompt as reference material.

get_generation_status

Check the status of an asynchronous content generation started by create_content (with a blueprint) or by ask_content_assistant. Poll it with the generation_id until the run completes; once finished it returns the current document and the latest Content Assistant reply.

list_content

List all content documents visible to you as a single unified array, whether created from scratch or from a blueprint. Use a content_id to fetch full content or to create a share link. Pass a `search` query to rank results by semantic relevance instead of recency.

get_content

Retrieve the full markdown body of a content document by its content_id. Use it when you need to read a document's text to answer a question about it — not to show the user content they can already open in Marcora.

update_content

Update a content document by its content_id — edit the body, rename it, or change its stage, visibility, category, or project. Only the fields you supply change, and body updates replace the entire text, so read it first when splicing into existing content.

Workflows

create_workflow

Create a new reusable, multi-step workflow template for the team, optionally scheduled. Workflows start as drafts and require an explicit list of allowed tools; activate them with update_workflow once confirmed.

get_workflow

Fetch one workflow's full definition along with its triggers and latest run. Always call it before update_workflow so you can preserve the fields you are not changing.

get_workflow_runs

Inspect a workflow's run history — either a paginated list of runs, or the detailed step and tool-call logs for a single run. Useful for checking whether a workflow ran and for troubleshooting failures.

list_workflows

List the team's workflows, with optional status filter and name search. Use it to see existing workflows or to check for duplicate names before creating one.

run_workflow

Manually run a workflow, dispatching a live agent session. Returns the run record; check its status to see whether the run started, failed, or was skipped.

update_workflow

Make a partial update to a workflow template; only the fields you send change. Commonly used to activate, rename, archive, or edit a workflow's steps — call get_workflow first to see the current state.

Account

get_current_user_info

Return profile and subscription information for the current user, including their active team, plan, and remaining AI credits. Use it to personalize responses or check limits before creating content.

get_team_info

Always call when the user asks what team accounts they have, which teams they belong to / are on, or wants to switch teams — do NOT answer from memory or session context, which knows only the single currently-active team and will undercount. This tool is the only way to enumerate the full list. Returns every team you belong to, each with its full member roster. Read-only, no inputs.

set_active_team

Sets your active team — the team all subsequent Marcora tool calls operate against. Switching changes your active team everywhere for your account; the response returns `previous_team_id` so you can restore it afterward.

Context Intelligence

list_ci_findings

List Context Intelligence findings — issues Marcora's automated scans detected in your reference library (stale content, contradictions, outdated web sources, gaps). Newest-first; filter by status, severity, or scan type.

get_ci_finding

Fetch one Context Intelligence finding in full detail by its UUID — the full recommendation, the suggested fix, and which context items it involves.

update_ci_finding_status

Acknowledge, dismiss, or resolve a Context Intelligence finding after reviewing it. Records resolver + timestamp on resolve; does not itself apply the suggested fix (that's done in the web app).

trigger_health_audit_scan

Start a library-wide Context Intelligence health audit — an AI sweep of your context/reference items that produces findings. Consumes credits, plan-gated (Business/Command), runs in the background.

Context & Resources

get_brand_foundation

Return the team's Brand Foundation: company overview, brand voice, writing style, and writing examples. Call it whenever the user asks about, or wants you to use, their brand voice, company information, or writing style.

list_context_collections

List all context collections you can access. Collections group reference materials; use a collection's ID to add items to it or to target context retrieval.

update_brand_foundation

Overwrite one of the team's four Brand Foundation elements — company overview, brand voice, writing style, or writing examples — with new content. Always a full replace, so read the current value with get_brand_foundation first to confirm what's being replaced.

create_context_collection

Create a new context collection to group related reference materials for easier management and targeted retrieval. Use the returned ID with add_context to add items to the collection.

add_context

Add a new reference item to your context library, the source material that powers on-brand AI generation. Supply the body as pasted markdown, a one-off URL import, or a tracked live web page, and optionally file it under a collection or project.

update_context

Update an existing context item: change its name, body, collection, or project, or re-pull a tracked web page's content. Collection and project use full-replace semantics, so always pass both.

get_relevant_context

Search the team's context library and return the most relevant chunks for a prompt. Use it when you need to read context yourself to answer a question or ideate — not before create_content, which gathers context automatically.

list_context_items

List context items from the team's library, each with its collection, project, and a link to open it in Marcora. By default it returns all items you can see; private items you don't have access to are filtered out. Pass a `search` query to rank items by semantic relevance instead of recency.

Blueprints

list_blueprints

List all blueprints in your team's library, each with its content category. Use a blueprint's UUID with create_content to generate content from that template.

get_blueprint

Retrieve the full details of a specific blueprint by its UUID, including its content, AI-generated analysis, and metadata. Find blueprint UUIDs with list_blueprints.

create_blueprint

Create a reusable blueprint template from finished example content for generating content at scale. The AI analyzes your example and produces the supporting template fields. Use create_blueprint_draft instead if you want to iterate on the template with AI before publishing.

create_blueprint_draft

Create an AI-assisted blueprint draft from a prompt that the user can review and edit in Marcora before publishing. Use create_blueprint instead if you already have the finished template content.

finalize_blueprint_draft

Publish a previously created blueprint draft into a full, usable blueprint. This is the final step after the user reviews the draft produced by create_blueprint_draft.

list_community_blueprints

Browse community blueprints shared by other Marcora users, with name, summary, contributor, and category. Use a blueprint's ID to view its full details before importing.

get_community_blueprint_details

Get the full details of a community blueprint, including its example content and style guide. Use the ID from list_community_blueprints, and pass it to import_community_blueprint to add the blueprint to your team.

import_community_blueprint

Import a blueprint from the Marcora community exchange into your team's library. Once imported, use it like any of your own blueprints to generate content.

Reference

list_content_categories

List the content categories available to your team, such as GTM Messaging or Website & Blog. Use a category's ID when creating blueprints or content.

list_targeting_dimensions

List the team's targeting dimensions and their options, such as Buying Stage or Persona. Pass the option IDs to create_content to target generated content at specific audiences or stages.

Sharing

create_external_share

Create a public share link for a content document, optionally with an expiration date. Anyone with the link can view it without a Marcora account, and it won't be indexed by search engines.

convert_markdown_to_word_doc

Export markdown content as a downloadable Word (.docx) file. Useful when the user needs a Microsoft Word or Google Docs–compatible version of a document.

Projects

list_projects

List all projects visible to you. Projects organize content into workstreams; use a project's ID to fetch its details or to associate new content with it.

get_project

Get the details of a specific project, including its members, documents, context items, and brief. Find project IDs with list_projects.

create_project

Create a new project to organize content and context into a workstream, optionally with a brief supplied directly or generated by AI. Use the returned project ID to associate new content with the project.

update_project

Update mutable fields on an existing project, such as its name, visibility, status, or brief. Uses PATCH semantics, so only the fields you pass change.

Plans & Playbooks

list_plans

List plans visible to the authenticated user with filters and pagination.

get_plan

Fetch a single plan by UUID with linked references, context collections, targeting dimensions, and metadata.

create_plan

Create a new plan in the authenticated user's active team.

update_plan

Partial update of a plan: mutable fields and stage transitions.

produce_plan

Produce (generate) the actual content a plan describes — the MCP equivalent of the Generate button on the plans board.

list_playbooks

List all content playbooks visible to the caller in the current team. Returns summaries only — call get_playbook for a playbook's items.

get_playbook

Fetch one content playbook by id, including its full ordered list of items.

create_playbook

Create a reusable content playbook — an ordered template of content-plan items you can stamp out as a batch.

create_playbook_from_plans

Create a playbook by capturing existing content plans as reusable template items ("save what worked as a template").

update_playbook

Edit a content playbook. Pass only the fields to change; if items is provided it fully replaces the playbook's items and order.

instantiate_playbook

Run a playbook: create one content plan per playbook item, in order, as a batch.

Scroll to Top