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:| Transport | Endpoint | Purpose |
|---|---|---|
| SSE | /api/mcp/sse | Server-Sent Events (recommended for most clients) |
| HTTP | /api/mcp/mcp | Streamable HTTP transport |
Authentication
Product Graph uses OAuth for MCP authentication combined with an organization header to scope requests to your workspace.Add Product Graph to your MCP client
Organization Context
All MCP requests must include theX-Organization-Id header with your organization’s UUID:
Supported Clients
Cursor
Claude Code
Claude Desktop
Windsurf
VS Code
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
Client-Specific Setup
- Cursor
- Claude Code
- Claude Desktop
- Windsurf
- VS Code
~/.cursor/mcp.json: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.Available MCP Tools
Once connected, you’ll have access to 31 tools in your AI assistant. All tools use thepg_ prefix for easy identification.
Search Tool
pg_search
pg_search
product, capability, feature, requirement, acceptance_criterion, user_type, core_entity, pageRead Tools
All read tools support amode parameter:
concise(default): Returns a truncated preview (~500 chars)full: Returns complete content
pg_read_product
pg_read_product
concise for preview, full for complete contentpg_read_capability
pg_read_capability
pg_read_feature
pg_read_feature
pg_read_requirement
pg_read_requirement
pg_read_acceptance_criterion
pg_read_acceptance_criterion
pg_read_user_type
pg_read_user_type
pg_read_core_entity
pg_read_core_entity
List Tools
pg_list_capabilities
pg_list_capabilities
pg_list_features
pg_list_features
pg_list_requirements
pg_list_requirements
pg_list_acceptance_criteria
pg_list_acceptance_criteria
pg_list_user_types
pg_list_user_types
pg_list_core_entities
pg_list_core_entities
pg_list_pages
pg_list_pages
Create Tools
pg_create_capability
pg_create_capability
pg_create_feature
pg_create_feature
pg_create_requirement
pg_create_requirement
FUNCTIONAL (behaviors), NON_FUNCTIONAL (qualities), CONSTRAINT (limits), BUSINESS_RULE (policies)pg_create_acceptance_criterion
pg_create_acceptance_criterion
pg_create_user_type
pg_create_user_type
pg_create_core_entity
pg_create_core_entity
pg_create_page
pg_create_page
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.pg_edit_capability
pg_edit_capability
pg_edit_feature
pg_edit_feature
pg_edit_requirement
pg_edit_requirement
pg_edit_acceptance_criterion
pg_edit_acceptance_criterion
pg_edit_user_type
pg_edit_user_type
pg_edit_core_entity
pg_edit_core_entity
Example Workflows
Pull PRD context into your IDE
When implementing a feature, ask your AI assistant to fetch the relevant requirements:Navigate the product hierarchy
Explore your product structure from the IDE:Create new artifacts from your IDE
Quickly scaffold new product artifacts:Verify implementation against requirements
After writing code, validate it matches the spec:Make safe edits to requirements
Update specifications with tracked changes:Troubleshooting
Missing X-Organization-Id header
Missing X-Organization-Id header
- Ensure your MCP configuration includes the
--headerargument 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
User is not a member of this organization
User is not a member of this organization
- 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
Authentication errors (401 Unauthorized)
Authentication errors (401 Unauthorized)
MCP client not connecting
MCP client not connecting
- 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
OAuth authorization not appearing
OAuth authorization not appearing
Tools not appearing
Tools not appearing
- 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
Artifact not found errors
Artifact not found errors
- 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
- 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-Idheader - 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
- Model Context Protocol Specification
- Cursor MCP Documentation
- Claude Code MCP Documentation
- mcp-remote — SSE bridge for MCP clients