Discover available entity types and their fields (field names, types, options, lifecycle operations). Call this before creating or updating entities to learn what fields are available. Optionally filter by entityType.

Discover available note types (simple, conversation, opportunity) and their fields. Call this before creating or updating notes.

List Productboard entities of a given type. Supports filtering by name, owner, status, archived, parent. Returns paginated results — use pageCursor from response to get next page.

Get a single Productboard entity by its UUID. Returns full entity data including fields and relationships.

Create a new Productboard entity. Call get_entity_configurations first to discover available fields for the entity type. The fields object should match the field schemas from configuration.

Update an existing Productboard entity. Use 'fields' for simple field replacement, or 'patch' for granular operations (set, addItems, removeItems, clear). These are mutually exclusive. Note: addItems/removeItems on 'teams' is emulated client-side (read-merge-set) due to a PB API bug.

Permanently delete a Productboard entity. This cascades to all child entities and cannot be undone.

Search Productboard entities using POST with complex filters. Supports filtering by types, statuses, owners, parent, archived, and specific IDs. For name-based search use list_entities (its name filter does partial match and works reliably); the name filter here is forwarded to Productboard's API but is currently ignored by it (upstream issue, verified 2026-05).

Get all relationships for a Productboard entity (parent, children, links, blocking, etc.). Can optionally filter by relationship type or target.

Create a relationship between two Productboard entities.

Set or replace the parent of a Productboard entity. Uses PUT to replace any existing parent relationship.

Remove a relationship from a Productboard entity. Requires the relationship type and target entity ID.

List Productboard notes (also known as insights) with pagination and optional filters. Sorted by creation date (newest first). DEFAULT: returns processed + unprocessed notes that are NOT archived. To include archived notes set archived=true; to fetch only archived notes set archived=true and omit processed (v2 quirk: archived notes always report processed=false).

Get a single Productboard note by its UUID.

Create a new Productboard note (insight). Call get_note_configurations first to discover available fields and note types (simple, conversation).

Update an existing Productboard note. Use 'fields' for simple replacement or 'patch' for granular operations (set, clear, addItems, removeItems).

Permanently delete a Productboard note. This cannot be undone.

Get relationships for a Productboard note (linked customers, entities, etc.).

Link a Productboard note to a customer (user/company) or entity. For customer relationships, this replaces any existing customer link.

Set or replace the customer relationship on a note. Only accepts user or company targets.

Remove a relationship from a Productboard note.

DEPRECATED — will stop working on 2026-07-08 when Productboard sunsets API V1. V2 has no equivalent note-comments endpoint as of 2026-05 (last confirmed via API changelog). No workaround available; the comment feature will be removed in v2.0.0 alongside the V1 client cleanup. Continue using only if comments are critical AND you have a contingency for sunset.

Search Productboard notes (insights). Routes to V2 POST /notes/search by default; falls back to V1 GET /notes only when term (fulltext) is set or allTags has 2+ values (V2 supports neither). The last relative time window (e.g. '6m', '10d') is translated to V2 updatedAt.from automatically, so last alone no longer forces V1. V1 fallback path will break on 2026-07-08 (V1 sunset). The response shape differs by path: V1 returns rich objects with top-level displayUrl, followers, features; V2 returns {id, type, links{self,html}, fields{...}, relationships{...}}. Check the apiVersion field in the result, or whether returned notes have top-level displayUrl (v1) vs links.html (v2). DEFAULT: hides archived notes — set archived=true to include.

Bulk-fetch Productboard notes via V2 API with auto-pagination (~100/page). Safety limit: 5000 notes max. DEFAULT: returns processed + unprocessed notes that are NOT archived. To include archived notes set archived=true. V2 response shape: each note has top-level {id, type, links{self,html}, fields{...}, relationships{...}, createdAt, updatedAt, metadata}. NOTE: v2 no longer returns followers[], embedded comments, totalResults, or features[].importance. Use links.html in place of v1 displayUrl. Linked features are now under /notes/{id}/relationships (not inline) — use get_note_relationships per note if you need them.

DEPRECATED: use get_note instead. Kept as an alias for backwards compatibility during the V1→V2 migration. Now calls v2 GET /notes/{id} (same as get_note). V1-only fields no longer available: followers[], embedded comments[], features[].importance. The v1 displayUrl is now exposed as links.html on the returned note. This tool will be removed in the next major release (v2.0.0-cleanup, after the V1 sunset on 2026-07-08).

Resolve a Productboard note from any identifier: UUID, numeric ID, web UI URL, or deep link. Returns the v2 note (with links.html — the web UI URL, equivalent to v1 displayUrl). For numeric IDs, scans up to 500 most-recent notes (~5 pages) matching against links.html. Includes archived notes in the scan.

List Productboard workspace members. Optionally filter by role.

Get a single Productboard workspace member by UUID.

Retrieve member activity metrics from Productboard. Returns daily activity data per member including feature/note/board creation counts.