Skip to main content

​
Partner MCP Server — Developer Guide

Connect your AI client to the Syntropy Partner Analytics server for protocol performance insights.

​
Overview

The Partner MCP Server provides analytics tools for Shopify partners to monitor protocol performance, consumer behavior, and adherence trends. It runs alongside the consumer MCP server but uses separate authentication scopes.

​
Connection

PropertyValue
TransportStreamable HTTP
Endpointhttps://api.syntropyhealth.com/mcp/partner
AuthBearer token (Clerk JWT)
Required Scopespartner:read

​
Claude Desktop

Add to claude_desktop_config.json: 
{
  "mcpServers": {
    "syntropy-partner": {
      "url": "https://api.syntropyhealth.com/mcp/partner",
      "headers": {
        "Authorization": "Bearer YOUR_PARTNER_JWT"
      }
    }
  }
}

​
Tool Catalog

​
get_protocol_analytics

Get extended analytics for a protocol including churn risk, consumption rate, and projected demand.
ParameterTypeRequiredDescription
protocol_idintYesThe protocol’s database ID

​
get_partner_overview

Get a summary of all protocol performance across your portfolio. Returns average PDC, active users, average streak days, and total protocols. No parameters required.

​
get_protocol_timeline_view

Get weekly check-in timeline data for a protocol in a given month. Returns weekly buckets with taken/skipped/missed counts.
ParameterTypeRequiredDescription
protocol_idintYesThe protocol’s database ID
yearintYesYear (2020-2030)
monthintYesMonth (1-12)

​
get_protocol_sentiment_view

Get weekly sentiment distribution for a protocol in a given month. Returns weekly positive/negative/neutral note counts.
ParameterTypeRequiredDescription
protocol_idintYesThe protocol’s database ID
yearintYesYear (2020-2030)
monthintYesMonth (1-12)

​
partner_copilot

Ask the Shrine AI partner analytics copilot a question. Get AI-generated insights about your protocol performance.
ParameterTypeRequiredDescription
questionstrYesYour question about protocol analytics
protocol_idintNoOptional protocol ID to focus the analysis on

​
Rate Limits

OperationLimit
Read tools60 requests/minute
Write tools20 requests/minute

​
Error Handling

All tools return a JSON dict. On error: 
{
  "error": "Description of what went wrong"
}
Common errors:
  • "Authentication required" — missing or invalid JWT, or wrong scope
  • "Rate limit exceeded" — too many requests, wait and retry
  • "Service temporarily unavailable" — backend service issue

​
Discovery

  • Capabilities: GET /api/mcp/capabilities
  • Full docs: GET /api/mcp/docs
  • Agent discovery: GET /llms.txt
  • Health check: GET /api/health