strategy

Create and update Business Model Canvas data in strategy.* — business units, the 9 canvas blocks, typed business-unit relationships, assumptions, provenance sources, draft canvas snapshots, competitors and personas.

Endpoint	https://strategy.mcp.devfellowship.com/mcp
Tools	24
Backing data	strategy.business_units, .value_propositions, .customer_segments, .customer_relationships, .channels, .revenue_streams, .key_partners, .key_activities, .resources, .expense_categories, .business_unit_relationships, .assumptions, .sources, .artifact_sources, .canvas_snapshots, .competitors, .entities, .personas.

Connect

Add https://strategy.mcp.devfellowship.com/mcp to your client (see Getting Started) with your Authorization: Bearer <token> header.

Business units

Tool	Description
list_business_units	List strategy.business_units. Excludes archived rows unless include_archived: true. Optionally filter to children of a parent via parent_business_unit_id.
get_business_unit	Fetch one business unit by id.
create_business_unit	Create a business unit — the root entity every canvas block hangs off of.
update_business_unit	Partially update a business unit by id.
archive_business_unit	Set is_archived (default true; pass archived: false to unarchive). Soft flag only — child rows are untouched.

Canvas blocks

Tool

Description

set_canvas_block

Upsert a row into one of the 9 BMC block tables (value_proposition, customer_segment, customer_relationship, channel, revenue_stream, key_partner, key_activity, key_resource, expense_category) for a business_unit_id. Pass id to update, omit to insert. fields maps straight to the target table’s columns — key_partner and key_resource (resources table) accept free-text name (+ description for key_resource), added 2026-07-15 via dfl-schema #683 to fix the “Unnamed Partner” display bug.

Relationships

Tool	Description
add_business_unit_relationship	Create a typed edge in strategy.business_unit_relationships between two business units (from_bu → to_bu), e.g. “funds”, “commercializes”, “supplies_talent”.

Assumptions

Tool	Description
add_assumption	Record a testable strategic assumption (desirability/viability/feasibility), its status, evidence, and risk if wrong.

Provenance

Tool	Description
add_source	Record a strategy.sources row — where a piece of strategy data came from (a Fireflies call, a plans.devfellowship.com plan, a Company Brain node, or a manual note).
link_artifact_source	Link any strategy.* artifact row (by table + id) to a source created via add_source.

Snapshots

Tool	Description
create_canvas_snapshot	Assemble a business unit’s full canvas (business unit + all 9 blocks + active relationships + assumptions) into a strategy.canvas_snapshots row, status: "draft". Version auto-increments per business unit.

Competitors, personas and customer segments

Tool	Description
add_competitor	Create a strategy.competitors row for a business unit, linked to a strategy.entities row (pass entity_id, or entity_name to create the entity inline).
add_persona	Create a strategy.personas row under a customer segment (occupation, buying role, ICP priority).
list_personas	List personas. Filter by customer_segment_id (direct) or business_unit_id (joins through customer_segments to cover every segment of the BU).
update_persona	Partially update a persona by id (including re-parenting to a different customer_segment_id).
delete_persona	Hard-delete a persona by id — strategy.personas has no soft-delete flag. Use to clean up misparented/duplicate personas.
list_customer_segments	List strategy.customer_segments rows for a business_unit_id.
update_customer_segment	Partially update a customer segment by id.
delete_customer_segment	Hard-delete a customer segment by id. See the RLS caution below — customer_segments currently has no DELETE policy.

Writing patterns (voice slots)

Tool	Description
list_writing_patterns	List strategy.writing_patterns rows for a business_unit_id, ordered by sort_order. Optionally narrow to one slot. Each row is a “voice slot” — a reusable definition of how a given surface should sound.
upsert_writing_pattern	Create or update one voice slot. Pass id to update that exact row, or slot to update-or-insert by slot. pattern is free-form jsonb and replaces the stored object (no deep merge).

SEO keywords

Tool	Description
list_keywords	List strategy.keywords (the SEO keyword corpus) of one business_unit_id. count is the exact corpus size of that BU, independent of limit.
delete_keywords	Hard-delete keywords by id, scoped to one business_unit_id. Metrics and relations cascade. Returns deleted_ids and not_deleted_ids. The cleanup path for e2e specs, which delete every keyword they create.
upsert_keywords	Create keywords in one business_unit_id (up to 200 per call), each with optional cluster_name / cluster_color, a keyword_metrics snapshot, and a parent_text for the mind-map tree. Identity is (business_unit_id, slug) with the campaigns app slugifier. Existing keywords are reused and left unchanged unless update_existing is true. Idempotent: re-run the same batch after a partial failure.

Read before you write — pattern is an unversioned convention, not a schema

strategy.writing_patterns.pattern is free-form jsonb. The rows in use today share a convention (description, toneAxes[], vocabularyDo[], vocabularyAvoid[], examplePairs[], notes) that the BM Canvas UI reads, but nothing enforces it and the column defaults to '[]'::jsonb. Call list_writing_patterns first and mirror the shape already in use, so a consumer reading every slot keeps working. Add extra keys only when a slot genuinely needs them — never drop the shared ones.

Agents cannot ratify a canvas snapshot

create_canvas_snapshot only ever creates status: "draft" rows. strategy.canvas_snapshots UPDATE (the draft → ratified transition) is gated at the database level to iam.is_global_admin() — there is deliberately no ratify_canvas_snapshot tool. Ratification happens in the BM Canvas app by a human global admin.

RLS write gap on the 7 non-segment canvas blocks — RESOLVED 2026-07-15

All 9 BMC blocks (value_proposition, customer_segment, customer_relationship, channel, revenue_stream, key_partner, key_activity, key_resource, expense_category) now have INSERT/UPDATE RLS policies for authenticated members (dfl-schema migration 20261906180000_strategy_block_tables_write_rls.sql) — set_canvas_block is agent-writable end to end on every block.

No DELETE policy on strategy.customer_segments

strategy.customer_segments has SELECT/INSERT/UPDATE policies for authenticated members but no DELETE policy — delete_customer_segment will likely fail with a Postgres RLS/permission error until a dfl-schema migration adds one. strategy.personas already has DELETE (permissive, no member check), so delete_persona works today.

user-JWT only — never service_role

Every tool on this page authenticates with the caller’s Supabase user JWT (RLS-scoped). None of them use service_role, per the fleet-wide rule that MCP tools carry the calling user’s own privileges — writes are exactly as permitted (or blocked) by the RLS policies above.