Skip to main content

Suppevo MCP Server

An MCP (Model Context Protocol) server that exposes the Suppevo supplement-tracking platform API as tools for AI assistants.

Features

Category Description
Profile Manage user profiles and preferences
Products CRUD, bulk operations, search (admin + public)
Supplements Track user supplement routines
Schedules Dosing schedules with reminders
Doses Log and query dose history
Reviews Create, moderate, and browse reviews
Rewards Points, badges, streaks, challenges
Brands Brand management and discovery
Brand Owners Brand owner portal tools
Ingredients CRUD, search, bulk ops, intelligence
Ingredient Intelligence Alternatives, interactions, dosing guides, effectiveness
Biomarkers Admin and public biomarker data
Evidence Links Scientific evidence management
Benefits Health benefit categories
Scoring Product and ingredient scoring
Stack Analysis Analyze supplement stacks
Suggestions User and admin suggestion workflows
News Public news feed
Exports Data export tools
Admin User groups, brand assignments

Quick Start

Prerequisites

  • Python 3.11+
  • A Suppevo API token (JWT from Cognito)

Install from PyPI

pip install suppevo-mcp

Or run directly with uvx (no install needed):

uvx suppevo-mcp

Install from source

git clone https://github.com/GomezMera-IO-LLC/suppevo-data-mcp.git
cd suppevo-data-mcp
pip install -e .

Configuration

The server loads environment variables from ~/.env (your home directory). This keeps credentials out of project files and version control.

Setup your ~/.env

Create or edit ~/.env:

# Suppevo MCP Server
SUPPEVO_API_TOKEN=your-jwt-token-here
SUPPEVO_REFRESH_TOKEN=your-refresh-token-here
SUPPEVO_CLIENT_ID=your-cognito-client-id
# SUPPEVO_API_BASE_URL=https://dev.api.suppevo.com/
# SUPPEVO_COGNITO_REGION=us-east-1
Variable Required Default Description
SUPPEVO_API_TOKEN Yes — JWT access token for authenticated endpoints
SUPPEVO_REFRESH_TOKEN No — Cognito refresh token for auto-renewal
SUPPEVO_CLIENT_ID No — Cognito app client ID (needed for token refresh)
SUPPEVO_API_BASE_URL No https://dev.api.suppevo.com/ API base URL
SUPPEVO_COGNITO_REGION No us-east-1 AWS region for Cognito

Note: Environment variables passed directly (e.g. via MCP client env config) take precedence over values in ~/.env.

Getting your API token

  1. Sign in to the Suppevo app
  2. Retrieve your JWT token from the authenticated session (IdToken from Cognito)
  3. Optionally grab the refresh token and client ID for automatic token renewal

MCP Client Setup

Kiro

Add to .kiro/settings/mcp.json:

{
  "mcpServers": {
    "suppevo": {
      "command": "uvx",
      "args": ["suppevo-mcp"]
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "suppevo": {
      "command": "uvx",
      "args": ["suppevo-mcp"]
    }
  }
}

Credentials are loaded automatically from ~/.env — no need to put tokens in MCP config files.

Running from source (development)

If you cloned the repo and want to point your MCP client at the local code:

{
  "mcpServers": {
    "suppevo": {
      "command": "python3",
      "args": ["-m", "suppevo_mcp"],
      "cwd": "/path/to/suppevo-data-mcp"
    }
  }
}

Usage

Once configured, your AI assistant will have access to all Suppevo tools. Examples:

  • "Search for magnesium supplements"
  • "Show my current supplement stack"
  • "Log a dose of Vitamin D — 5000 IU taken this morning"
  • "What are the interactions for ashwagandha?"
  • "Create a new product called 'Omega-3 Fish Oil' in the heart category"
  • "Show my points balance and current streak"

Public vs Authenticated Tools

  • Public tools (prefixed with public_) work without authentication and are read-only
  • Authenticated tools require SUPPEVO_API_TOKEN and provide full CRUD access
  • Admin tools require an admin-level token for write operations on products, brands, ingredients, etc.

Token Refresh

If you provide SUPPEVO_REFRESH_TOKEN and SUPPEVO_CLIENT_ID, the server will automatically refresh expired access tokens via AWS Cognito. This prevents interruptions during long sessions.

Without a refresh token, you'll see a 401 error when the token expires and will need to update the token in your MCP config and restart.

Development

# Install in editable mode
pip install -e .

# Run the server directly
python3 -m suppevo_mcp

# Test with MCP inspector
npx @modelcontextprotocol/inspector python3 -m suppevo_mcp

Transport

The server uses stdio transport by default, which is the standard for MCP client integrations.

License

MIT

Metadata

Release files for suppevo-data-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for suppevo-data-mcp 0.1.0
File Size Uploaded Provenance
suppevo_data_mcp-0.1.0.tar.gz 37.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for suppevo-data-mcp 0.1.0
File Interpreter ABI Platform
suppevo_data_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 63.7 kB

Release files / suppevo_data_mcp-0.1.0.tar.gz

Download URL suppevo_data_mcp-0.1.0.tar.gz
Size 37.4 kB
Tags Source
SHA-256 checksum
How to use checksums
6dd774b8f5c98ca0a812911f5ec1fa2784641572434499f96e123d4ac9674a74
BLAKE2b-256 checksum
How to use checksums
90ca8b1b874926e641dc590182d17cac1c28367b26b9fdffc0aa1cfb63ec6ef4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Release files / suppevo_data_mcp-0.1.0-py3-none-any.whl

Download URL suppevo_data_mcp-0.1.0-py3-none-any.whl
Size 26.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8786a95e91a4df6e9a54c080f8ab2b983da9b16b1a829d99970fa13f092cb7c6
BLAKE2b-256 checksum
How to use checksums
eb3c4429e7dcdb520f8190c63ccdeae2eb10ffb7bb5b7a05205187a75050e690
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.14.3

Security for suppevo-data-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page