Skip to main content
Product Graph’s MCP server lets you securely connect your product knowledge directly to AI coding assistants like Cursor, Claude Code, Windsurf, and more. Access your PRDs, requirements, and product context without leaving your development environment.

Overview

The Model Context Protocol (MCP) is an open standard that allows AI assistants to securely access external data sources. With Product Graph’s MCP integration, you can:
  • Search product artifacts — Find PRDs, capabilities, features, requirements, and more from your IDE
  • Read document content — Pull full context into your coding sessions in markdown format
  • Create new artifacts — Build out your product hierarchy directly from your IDE
  • Edit documents safely — Apply patch-style edits with full version history and rollback support
  • Stay in sync — Always work with the latest product requirements

MCP Endpoint

Product Graph’s MCP server is hosted at:
https://app.productgraph.ai/api/mcp/sse
The server supports multiple transport types:
TransportEndpointPurpose
SSE/api/mcp/sseServer-Sent Events (recommended for most clients)
HTTP/api/mcp/mcpStreamable HTTP transport

Authentication

Product Graph uses OAuth for MCP authentication combined with an organization header to scope requests to your workspace.
1

Add Product Graph to your MCP client

Configure your MCP client with the Product Graph endpoint and your organization ID (see setup instructions below).
2

Authorize access

When prompted, sign in to your Product Graph account and authorize the connection.
3

Start using MCP tools

Once authorized, you’ll have access to all Product Graph tools with your existing permissions.

Organization Context

All MCP requests must include the X-Organization-Id header with your organization’s UUID:
X-Organization-Id: <your-organization-uuid>
This header scopes all operations to your specific workspace. You can find your organization ID in the MCP Connection modal in Product Graph.
Your MCP session inherits your Product Graph permissions—you’ll only be able to access artifacts in workspaces you have access to.

Supported Clients

Cursor

Via mcp-remote bridge

Claude Code

CLI with SSE transport

Claude Desktop

Via mcp-remote bridge

Windsurf

Via mcp-remote bridge

VS Code

Via mcp-remote bridge

Get Your Configuration

Quick Setup from Product GraphOpen the MCP Connection modal in Product Graph to get your configuration:
  • Use the one-click install button for Cursor
  • Copy the Claude Code CLI command with your organization ID pre-filled
  • Or copy the full JSON configuration for manual setup
You can also access this anytime by clicking the MCP button in the sidebar.

Client-Specific Setup

Add the following to your MCP configuration file at ~/.cursor/mcp.json:
{
  "mcpServers": {
    "product-graph": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.productgraph.ai/api/mcp/sse",
        "--header",
        "X-Organization-Id: YOUR_ORGANIZATION_ID"
      ]
    }
  }
}
Replace YOUR_ORGANIZATION_ID with your organization UUID from the MCP Connection modal.Restart Cursor, and you’ll be prompted to authorize Product Graph when first connecting.
Use the one-click install from the MCP Connection modal to automatically configure Cursor with your organization ID.

Available MCP Tools

Once connected, you’ll have access to 31 tools in your AI assistant. All tools use the pg_ prefix for easy identification.

Search Tool

Read Tools

All read tools support a mode parameter:
  • concise (default): Returns a truncated preview (~500 chars)
  • full: Returns complete content
Read the Product document for your organization. The Product is the root artifact containing vision, goals, and high-level product information.Parameters:
mode
string
default:"concise"
concise for preview, full for complete content
Read a Capability document content in markdown format.Parameters:
capabilityId
string
required
Capability UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read a Feature document content in markdown format.Parameters:
featureId
string
required
Feature UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read a Requirement document content in markdown format.Parameters:
requirementId
string
required
Requirement UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read an Acceptance Criterion document content in markdown format.Parameters:
acceptanceCriterionId
string
required
Acceptance Criterion UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read a User Type document content in markdown format.Parameters:
userTypeId
string
required
User Type UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read a Core Entity document content in markdown format.Parameters:
coreEntityId
string
required
Core Entity UUID to read
mode
string
default:"concise"
concise for preview, full for complete content
Read a Page document content in markdown format.Parameters:
pageId
string
required
Page UUID to read
mode
string
default:"concise"
concise for preview, full for complete content

List Tools

List all Capabilities under the Product.Parameters:
productId
string
required
Parent Product UUID
List all Features under a Capability.Parameters:
capabilityId
string
required
Parent Capability UUID
List all Requirements under a Feature.Parameters:
featureId
string
required
Parent Feature UUID
List all Acceptance Criteria under a Requirement.Parameters:
requirementId
string
required
Parent Requirement UUID
List all User Types under the Product.Parameters:
productId
string
required
Parent Product UUID
List all Core Entities under the Product.Parameters:
productId
string
required
Parent Product UUID
List all Pages in the workspace.Parameters:
folderId
string
Optional folder UUID to filter pages by folder

Create Tools

Create a new Capability under the Product. The Capability will be initialized with a default document template.Parameters:
productId
string
required
Parent Product UUID where the Capability should be created
Create a new Feature under a Capability. The Feature will be initialized with a default document template.Parameters:
capabilityId
string
required
Parent Capability UUID where the Feature should be created
Create a new Requirement under a Feature. The Requirement will be initialized with a default document template.Parameters:
featureId
string
required
Parent Feature UUID where the Requirement should be created
type
string
default:"FUNCTIONAL"
Requirement type: FUNCTIONAL (behaviors), NON_FUNCTIONAL (qualities), CONSTRAINT (limits), BUSINESS_RULE (policies)
Create a new Acceptance Criterion under a Requirement. The Acceptance Criterion will be initialized with a Given-When-Then template.Parameters:
requirementId
string
required
Parent Requirement UUID where the Acceptance Criterion should be created
Create a new User Type under the Product. The User Type will be initialized with a default template.Parameters:
productId
string
required
Parent Product UUID where the User Type should be created
Create a new Core Entity under the Product. The Core Entity will be initialized with a default template.Parameters:
productId
string
required
Parent Product UUID where the Core Entity should be created
Create a new Page in the workspace. The Page will be initialized with an empty document.Parameters:
folderId
string
Optional folder UUID to place the page in. If not provided, page will be created at root level.

Edit Tools

All edit tools use a unified diff patch format to make precise, reviewable changes to documents. Changes are tracked in version history and can be reviewed or rolled back in the Product Graph UI.
Edit a Capability document using a unified diff patch.Parameters:
capabilityId
string
required
Capability UUID to edit
patch
string
required
Unified diff patch to apply
Edit a Feature document using a unified diff patch.Parameters:
featureId
string
required
Feature UUID to edit
patch
string
required
Unified diff patch to apply
Edit a Requirement document using a unified diff patch.Parameters:
requirementId
string
required
Requirement UUID to edit
patch
string
required
Unified diff patch to apply
Edit an Acceptance Criterion document using a unified diff patch.Parameters:
acceptanceCriterionId
string
required
Acceptance Criterion UUID to edit
patch
string
required
Unified diff patch to apply
Edit a User Type document using a unified diff patch.Parameters:
userTypeId
string
required
User Type UUID to edit
patch
string
required
Unified diff patch to apply
Edit a Core Entity document using a unified diff patch.Parameters:
coreEntityId
string
required
Core Entity UUID to edit
patch
string
required
Unified diff patch to apply
Edit a Page document using a unified diff patch.Parameters:
pageId
string
required
Page UUID to edit
patch
string
required
Unified diff patch to apply

Example Workflows

Pull PRD context into your IDE

When implementing a feature, ask your AI assistant to fetch the relevant requirements:
Search for the checkout flow feature and read its requirements
Explore your product structure from the IDE:
Read the product to get the productId, then list all capabilities

Create new artifacts from your IDE

Quickly scaffold new product artifacts:
Create a new feature under capability xyz789 for user notifications

Verify implementation against requirements

After writing code, validate it matches the spec:
Read the acceptance criteria for requirement def456 and check if my implementation covers all cases

Make safe edits to requirements

Update specifications with tracked changes:
Read requirement abc123, then update the acceptance criteria to include error handling

Troubleshooting

  • Ensure your MCP configuration includes the --header argument with your organization ID
  • Copy the configuration from the MCP Connection modal which includes your organization ID
  • Verify the organization ID is a valid UUID format
  • The organization ID in your configuration doesn’t match a workspace you have access to
  • Get the correct organization ID from the MCP Connection modal in Product Graph
  • Ensure you’re signed in to the same Product Graph account you authorized with
  • Re-authorize Product Graph by removing and re-adding the MCP connection
  • Ensure you’re signed in to the correct Product Graph account
  • Your OAuth session may have expired—reconnecting will refresh it
  • Verify the endpoint URL is correct: https://app.productgraph.ai/api/mcp/sse
  • Ensure Node.js is installed (required for npx mcp-remote)
  • Check that your client’s MCP configuration is valid JSON
  • Try restarting your IDE after configuration changes
  • Check that popups aren’t blocked in your browser
  • Try manually opening the authorization URL if provided
  • Restart your MCP client and try connecting again
  • Restart your MCP client after configuration
  • Verify the JSON syntax is correct (no trailing commas)
  • Check your client’s MCP logs for error messages
  • Ensure you’ve completed the OAuth authorization flow
  • Verify the artifact ID is a valid UUID
  • Ensure the artifact exists in your organization
  • Check that your account has access to the workspace containing the artifact

Security

Product Graph’s MCP integration follows security best practices:
  • HTTPS only — All connections use secure TLS transport
  • OAuth authentication — Industry-standard OAuth 2.0 with secure token handling
  • Organization scoping — All operations are scoped to your organization via the X-Organization-Id header
  • Permission parity — MCP operations use the same permissions as the Product Graph UI
  • Membership validation — Server validates that you are a member of the specified organization
  • Audit trail — All changes are tracked in version history with full attribution
  • No credential storage — OAuth tokens are managed by your MCP client, not stored in config files

Version History & Rollback

All changes made through MCP are fully auditable:
  • Tracked changes — Edit operations create tracked changes visible in the Product Graph UI
  • Attribution — All changes are attributed to your user account
  • Version history — View the complete history of changes to any document
  • Rollback support — Restore previous versions through the Product Graph UI

Resources