Provides an AI agent with evidence-based supplement research, dosing, safety, and interaction analysis tools.
Also known as DrBaher/supstack-cli, supstack-cli, @supstack/cli
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.18.2
- Last commit
- Nov 15, 2026
- License
- MIT
What is supstack MCP?
supstack provides an AI agent with evidence-based supplement research, dosing, safety, and interaction analysis tools.
Summary generated from the project's README
About supstack MCP server
Providing evidence-based supplement research and safety analysis to AI agents is what supstack enables. It functions as a thin client over a public API, allowing users to access intelligence regarding supplement dosing, research studies, and potential interactions between supplements, medications, or specific pathways. The server can be run locally via stdio, making it compatible with clients like Claude Desktop or Claude Code.
Users can access the toolset anonymously for read-only tasks such as research, searching, and comparing supplements. For more personalized capabilities, users can log in to access account-scoped tools like profile management, personalized recommendations, and tracking adherence. The system includes built-in caching to manage rate limits and supports machine-readable JSON output for automated workflows. It provides specific tools for checking how different forms of a supplement, such as an injection route, might change safety advice.
What you can do with it
- 1Analyze supplement safetyAsk the agent to check if a specific supplement interacts with a prescribed medication or a biological pathway.
- 2Compare different supplementsRequest a head-to-head comparison between two different supplements to understand their differences.
- 3Research clinical evidenceHave the AI find randomized controlled trials or research summaries related to a specific health goal.
- 4Personalize supplement regimensUse account-linked tools to receive supplement recommendations based on a personal health profile.
Written from the project's README. Every use case is checked against a quote from it.
How to install supstack MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall supstack MCP in Claude Code
$ claude mcp add supstack-cli -- npx -y @supstack/cliInstall supstack MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"supstack-cli": {
"command": "npx",
"args": [
"-y",
"@supstack/cli"
]
}
}
}Install supstack MCP in VS Code
.vscode/mcp.json
{
"servers": {
"supstack-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@supstack/cli"
]
}
}
}Install supstack MCP in VS Code CLI
$ code --add-mcp '{"name":"supstack-cli","type":"stdio","command":"npx","args":["-y","@supstack/cli"]}'Install supstack MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"supstack-cli": {
"command": "npx",
"args": [
"-y",
"@supstack/cli"
]
}
}
}Install supstack MCP in Codex
$ codex mcp add supstack-cli -- npx -y @supstack/cliInstall supstack MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.supstack-cli] command = "npx" args = ["-y", "@supstack/cli"]
Install supstack MCP in Gemini CLI
$ gemini mcp add -s user supstack-cli npx -- -y @supstack/cliInstall supstack MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"supstack-cli": {
"command": "npx",
"args": [
"-y",
"@supstack/cli"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachabledrbaher/supstack-cli is public and reachablegithub.com/drbaher/supstack-cli ↗Pass
- Package names this repository as its source@supstack/cli names drbaher/supstack-cli as sourcenpmjs.com/package/@supstack/cli ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @supstack/clinpmjs.com/package/@supstack/cli/v/0.18.2#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/drbaher/supstack-cli ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @supstack/cliPass
- No critical advisory in the package or its dependencies100 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@supstack/cli
Evidence-based supplement intelligence in your terminal — and an MCP server for AI agents.
A thin client over the public SupStack API. Read-only, no account required. One capability registry powers both the CLI and the MCP server.
Status: Phase 2 (accounts) in progress. All read commands below work, plus an MCP server and
login/whoami. Install withnpm install -g @supstack/cli.
Install
# Homebrew (macOS / Linux)
brew install drbaher/supstack/supstack
# or npm
npm install -g @supstack/cli
# or run without installing
npx -y @supstack/cli define adaptogen
Then enable shell completion: supstack completion install.
From source (in this directory): npm install && npm run build && node dist/index.js define adaptogen.
Usage
supstack research magnesium --protocol # full evidence summary for one supplement
supstack search --goal deep-sleep -n 5 # search by name or filter
supstack compare magnesium glycine # 2–3 head-to-head
supstack studies "sleep" --type rct # research library
supstack interactions caffeine l-theanine --pathway # interaction check (deep pair analysis)
supstack interactions magnesium potassium --medication lisinopril # supplement × drug check
supstack interactions calcium --medication ibandronate --route injection # the form changes the advice
supstack stack add magnesium --dose 400mg --timing bedtime # local stack (+ dose/timing/brand)
supstack stack sync # sync local ⇄ your account (login required)
supstack goals --category sleep # list goal ids (for rate/recommend)
supstack rate --goals deep-sleep,sharpen-focus # grade your stack A–F by goal coverage
supstack experiments start magnesium deep-sleep # run an N-of-1 experiment (requires login)
supstack export --format md # export your stack
supstack define bioavailability # glossary lookup
supstack <command> --json # machine-readable output on any command
supstack --help
Account (Phase 2)
supstack login # sign in via device-code flow (opens the browser to confirm)
supstack whoami # show the signed-in account
supstack logout # sign out and revoke this device's token
login shows a one-time code, opens https://supstack.me/activate, and finishes
once you approve in the browser. The token lives in ~/.supstack/config.json
(0600). Reads work fully anonymously — an account unlocks personalized features.
Once logged in, sync your stack with your account:
supstack stack pull # local ← your account
supstack stack push # local → your account (keeps dosage/timing/brand for kept items)
supstack stack sync # additive merge of both; preserves existing cloud metadata
supstack profile # view your health profile
supstack profile set --age 35 --sex male --weight 80 --weight-unit kg
supstack profile set --smoking former # never | former | current — gates beta-carotene
supstack recommend # personalized picks from your goals + stack
supstack experiments list # your N-of-1 experiments + verdicts
supstack track log # log today's stack as taken
supstack track adherence # your adherence rate, streak, per-supplement
As an MCP server
supstack mcp # stdio MCP server exposing all capabilities as tools
This gives an agent the full SupStack toolset. Read-only (no account needed):
supstack_research, supstack_search, supstack_compare, supstack_studies,
supstack_interactions, supstack_stack, supstack_rate_stack, supstack_export,
supstack_define.
Account-scoped tools are also exposed — supstack_recommend,
supstack_profile_get / supstack_profile_set, supstack_experiments_list /
supstack_experiments_get, supstack_track_log, supstack_track_adherence
(plus cloud supstack_stack pull/push/sync). These require the user to be signed
in (supstack login, or a SUPSTACK_TOKEN); without a token they return a clear
"not logged in" error rather than failing. Mutating tools (profile_set,
track_log) are flagged readOnlyHint: false for the agent.
Claude Code (one command):
claude mcp add supstack -- supstack mcp
Claude Desktop — add to claude_desktop_config.json
(macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"supstack": {
"command": "supstack",
"args": ["mcp"]
}
}
}
Or run it without a global install via
"command": "npx", "args": ["-y", "@supstack/cli", "mcp"]. To use a local checkout, point at the built entrypoint —"command": "node", "args": ["/absolute/path/to/supstack-cli/dist/index.js", "mcp"](runnpm run buildfirst).
Configuration
| Env var | Default | Purpose |
|---|---|---|
SUPSTACK_API_URL |
https://supstack.me/api/v1 |
API base URL (override for local dev) |
SUPSTACK_API_KEY |
— | Optional API key (anonymous works at 60/min/IP) |
SUPSTACK_CACHE_TTL |
3600 |
Response cache TTL in seconds |
SUPSTACK_NO_CACHE |
— | Set to disable the response cache |
SUPSTACK_TIMEOUT |
20 |
Per-request timeout in seconds (or use --timeout) |
SUPSTACK_HOME |
~/.supstack |
Directory for config, stack, and cache |
SUPSTACK_TOKEN |
— | Override the stored account token (from supstack login) |
SUPSTACK_NO_ANON_TOKEN |
— | Disable auto-minting of the anonymous instant-token |
SUPSTACK_NO_UPDATE_CHECK |
— | Disable the "update available" notice (also honours NO_UPDATE_NOTIFIER) |
NO_COLOR |
— | Disable ANSI colour |
FORCE_COLOR |
— | Force ANSI colour on (even when piped) |
Global flags available on any command: --json, --no-cache, --timeout <seconds>, --color / --no-color, -q, --quiet.
supstack auth set-key <key> persists a key to ~/.supstack/config.json (written 0600).
Response cache
Read-only API responses are cached under ~/.supstack/cache/ (1-hour TTL by
default) to keep repeat lookups well under the 60/min rate limit. Bypass it per
command with --no-cache, or manage it with supstack cache clear /
supstack cache path. The cache is bounded (oldest entries pruned past a cap).
Shell completion
One-step install for your current shell (writes the script and wires your rc file
idempotently; uninstall reverses it):
supstack completion install # detects bash | zsh | fish from $SHELL
…or generate the script yourself:
supstack completion bash >> ~/.bashrc
supstack completion zsh > "${fpath[1]}/_supstack"
supstack completion fish > ~/.config/fish/completions/supstack.fish
Completions are dynamic — the script forwards what you've typed to
supstack __complete, which offers the right thing for the position:
- top-level commands and sub-actions (
stack <TAB>→add remove list pull push sync) - supplement slugs where a slug is expected (
research <TAB>,compare a <TAB>,stack add <TAB>,track log <TAB>) - goal ids after
search --goal <TAB>
Slug/goal lists are fetched once from the API and cached under
~/.supstack/completion/ (24-hour TTL). Pre-warm or refresh them with:
supstack completion refresh
Exit codes
Commands exit with a semantic code so scripts and MCP wrappers can branch on the kind of failure:
| Code | Meaning |
|---|---|
0 |
Success |
1 |
Generic error (incl. 5xx) |
2 |
Auth required/rejected (not logged in, 401, 403) |
3 |
Not found (404) |
4 |
Rate limited (429) |
5 |
Network failure / timeout |
6 |
Invalid input (bad/missing args or flags, unknown command, schema validation, 400/422) |
Develop
npm test # unit tests (mocked fetch)
npm run type-check # tsc --noEmit
npm run build # tsup → dist/
See CLAUDE.md for the capability pattern and how to add a command.
License
MIT
supstack MCP questions
How do I add supstack MCP to Claude Code?
Run claude mcp add supstack-cli -- npx -y @supstack/cli in your terminal. Add --scope user to make it available in every project.
How do I add supstack MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can I use supstack with Claude Desktop?
You can add it to your claude_desktop_config.json file using the 'supstack mcp' command or via npx.