Skip to content

chore: claim lobehub hevy-mcp - #712

Merged
chrisdoc merged 1 commit into
mainfrom
chrisdoc/lobe
Jul 20, 2026
Merged

chore: claim lobehub hevy-mcp#712
chrisdoc merged 1 commit into
mainfrom
chrisdoc/lobe

Conversation

@chrisdoc

@chrisdoc chrisdoc commented Jul 20, 2026

Copy link
Copy Markdown
Owner

✨ PR Description

Purpose: Register Hevy MCP Server plugin with LobeHub ecosystem by creating plugin manifest and changelog entry.

Main changes:

  • Added plugin manifest with metadata, cloud endpoint, and MCP server configuration for Hevy fitness integration
  • Created changeset file to track version release (3.3.0) for LobeHub plugin registry

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how

Summary by CodeRabbit

  • Chores

    • Updated the plugin metadata and version to 3.3.0.
    • Added release tracking information for this update.
  • Documentation

    • Refreshed the published plugin manifest details, including its description, links, categorization, and supported endpoints.

@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Jul 20, 2026

Copy link
Copy Markdown

Code Review by Qodo

Grey Divider

New Review Started

This review has been superseded by a new analysis

Grey Divider

Qodo Logo

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a changeset file and a new plugin manifest, lhm.plugin.json, for the Hevy MCP Server. Feedback is provided regarding a version mismatch in the manifest file, which should be updated to match the package version.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread lhm.plugin.json
"identifier": "chrisdoc-hevy-mcp",
"name": "Hevy MCP Server",
"tags": ["hevy", "fitness", "workouts", "health", "mcp"],
"version": "3.3.0"

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There is a version mismatch between lhm.plugin.json (3.3.0) and package.json (3.4.0). Please update the version in the plugin manifest to match the current package version.

Suggested change
"version": "3.3.0"
"version": "3.4.0"

@coderabbitai

coderabbitai Bot commented Jul 20, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e0800115-f7d0-4934-bd14-f96465d4f9cc

📥 Commits

Reviewing files that changed from the base of the PR and between c6b2587 and c9db403.

📒 Files selected for processing (2)
  • .changeset/old-cobras-stop.md
  • lhm.plugin.json

📝 Walkthrough

Walkthrough

The plugin manifest is updated with version 3.3.0 and metadata fields, and an empty changeset file is added.

Changes

Plugin release metadata

Layer / File(s) Summary
Manifest and changeset updates
lhm.plugin.json, .changeset/old-cobras-stop.md
The manifest defines plugin metadata and version 3.3.0; the changeset file contains only blank lines.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

I’m a rabbit hopping through release notes bright,
A plugin version takes wing tonight.
The manifest shines, the fields align,
While an empty changeset waits in line.
Hop, hop—3.3.0 looks fine!

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chrisdoc/lobe

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chrisdoc
chrisdoc merged commit f6612a3 into main Jul 20, 2026
14 of 17 checks passed
@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Add LobeHub plugin manifest for Hevy MCP server

⚙️ Configuration changes 🕐 Less than 10 minutes

Grey Divider

AI Description

• Add LobeHub plugin manifest metadata for the Hevy MCP server.
• Introduce a changeset entry to satisfy release/registry workflow requirements.
Diagram

graph TD
  A["Repo"] --> B["lhm.plugin.json"] --> C(["LobeHub/Registry"])
  C --> D(["Hevy MCP endpoint"])
  
  subgraph Legend
    direction LR
    _file["File"] ~~~ _svc(["Service"]) ~~~ _ext(["External endpoint"])
  end
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Use a fully-populated Changesets entry (package bump + summary)
  • ➕ Aligns with standard Changesets expectations and avoids CI/release ambiguity
  • ➕ Documents why the version should change and which package is impacted
  • ➖ Requires knowing the correct package name(s) and intended bump type
2. Generate/validate manifest via a schema (JSON Schema or lint step)
  • ➕ Prevents publishing malformed metadata (e.g., missing/invalid fields)
  • ➕ Makes future edits safer and easier to review
  • ➖ Adds tooling/config overhead to the repo

Recommendation: Keep the manifest approach (it’s the right shape for a registry claim), but ensure the Changesets file is valid and intentional. As-is, the changeset content appears to be placeholder ('---' only); consider replacing it with a standard Changesets frontmatter block that specifies the affected package(s), bump type, and a short summary. Optionally add a lightweight schema/lint step to prevent malformed registry metadata.

Files changed (2) +15 / -0

Other (2) +15 / -0
old-cobras-stop.mdAdd changeset entry for release/registry workflow +2/-0

Add changeset entry for release/registry workflow

• Introduces a new Changesets markdown file. The current content appears to be placeholder frontmatter separators and may need package/bump details to be actionable.

.changeset/old-cobras-stop.md

lhm.plugin.jsonAdd LobeHub plugin manifest for Hevy MCP server +13/-0

Add LobeHub plugin manifest for Hevy MCP server

• Adds plugin metadata including author details, category, tags, and version. Points LobeHub clients/registry to the hosted MCP endpoint via the cloudEndpoint field.

lhm.plugin.json

@chrisdoc
chrisdoc deleted the chrisdoc/lobe branch July 20, 2026 10:02
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Register/claim Hevy MCP server for LobeHub

⚙️ Configuration changes 🕐 Less than 10 minutes

Grey Divider

AI Description

• Add LobeHub plugin manifest for the Hevy MCP Server (metadata + cloud endpoint).
• Add a Changesets entry to publish the registry/metadata update.
Diagram

graph TD
  R["Repo"] --> M["lhm.plugin.json"] --> L["LobeHub registry"] --> C["MCP clients"] --> S["Hevy MCP server"] --> H{{"Hevy API"}}
  M -. "cloudEndpoint" .-> S
  subgraph Legend
    direction LR
    _cfg["Config/metadata"] ~~~ _svc["Service"] ~~~ _ext{{"External"}}
  end
Loading
High-Level Assessment

The approach (adding a dedicated plugin manifest with a hosted cloud endpoint and a Changesets entry) is the standard/lowest-friction way to claim/register a LobeHub MCP listing. Main reviewer checks: ensure the Changesets file has the expected frontmatter/content for the repo’s release process, and that the manifest version aligns with the intended published version.

Files changed (2) +15 / -0

Other (2) +15 / -0
old-cobras-stop.mdAdd Changesets entry for the registry update +2/-0

Add Changesets entry for the registry update

• Introduces a new Changesets markdown file to track/publish the change via the repo’s release automation.

.changeset/old-cobras-stop.md

lhm.plugin.jsonAdd LobeHub plugin manifest for Hevy MCP Server +13/-0

Add LobeHub plugin manifest for Hevy MCP Server

• Adds a new LobeHub plugin manifest defining author metadata, category/tags, hosted MCP cloud endpoint, and the current version for the Hevy MCP Server listing.

lhm.plugin.json

@github-actions

Copy link
Copy Markdown
Contributor

MCP tool token cost

Measured with o200k_base over the complete json-serialized mcp tools/list result payload: { tools }.
Targets are advisory and never fail CI.

Metric Current Target Status
Tools 25 ≤ 20 Above target
Total tokens 12667
Average tokens/tool 506.68 < 600 Within target

Change from baseline

Metric Baseline Current Delta
Tools 25 25 0
Total tokens 12667 12667 0
Average tokens/tool 506.68 506.68 0

Per-tool changes

Tool Baseline Current Delta
create-body-measurement 669 669 0
create-exercise-template 421 421 0
create-routine 564 564 0
create-routine-folder 166 166 0
create-workout 655 655 0
get-body-measurement 628 628 0
get-body-measurements 629 629 0
get-exercise-history 808 808 0
get-exercise-template 276 276 0
get-exercise-templates 308 308 0
get-routine 552 552 0
get-routine-folder 245 245 0
get-routine-folders 270 270 0
get-routines 586 586 0
get-training-summary 923 923 0
get-user-info 244 244 0
get-workout 522 522 0
get-workout-count 195 195 0
get-workout-events 670 670 0
get-workouts 540 540 0
search-exercise-templates 426 426 0
search-routines 465 465 0
update-body-measurement 667 667 0
update-routine 562 562 0
update-workout 672 672 0

Per-tool breakdown

Tool Tokens Share of total
get-training-summary 923 7.29%
get-exercise-history 808 6.38%
update-workout 672 5.31%
get-workout-events 670 5.29%
create-body-measurement 669 5.28%
update-body-measurement 667 5.27%
create-workout 655 5.17%
get-body-measurements 629 4.97%
get-body-measurement 628 4.96%
get-routines 586 4.63%
create-routine 564 4.45%
update-routine 562 4.44%
get-routine 552 4.36%
get-workouts 540 4.26%
get-workout 522 4.12%
search-routines 465 3.67%
search-exercise-templates 426 3.36%
create-exercise-template 421 3.32%
get-exercise-templates 308 2.43%
get-exercise-template 276 2.18%
get-routine-folders 270 2.13%
get-routine-folder 245 1.93%
get-user-info 244 1.93%
get-workout-count 195 1.54%
create-routine-folder 166 1.31%

Per-tool counts encode each complete tool object independently. The total encodes the complete { tools } envelope, so punctuation and separators mean the per-tool values need not sum exactly to the total.

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Bundle Report

Bundle size has no change ✅

@gitstream-cm gitstream-cm Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✨ PR Review

The PR adds a new Hevy MCP plugin registration entry and an accompanying empty changeset. The plugin JSON looks well-structured, but the changeset does not follow the project's stated convention for user-facing changes.

1 issues detected:

🧹 Maintainability - `npx changeset --empty` was used for a user-facing registry addition; a versioned changeset with a package bump is required instead.

Details: The changeset file is empty (just the YAML front-matter delimiters with no package/version bump entries). According to the project's contribution rules, an empty/no-op changeset is reserved for internal-only changes such as docs, CI, tests, and refactors. Adding a new publicly-discoverable plugin to the registry is a user-facing, runtime-visible change and should carry a proper versioned changeset.

File: .changeset/old-cobras-stop.md (1-2)

Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Review using Guidelines Learn how

@codecov

codecov Bot commented Jul 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.45%. Comparing base (c6b2587) to head (c9db403).
⚠️ Report is 2 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #712   +/-   ##
=======================================
  Coverage   95.45%   95.45%           
=======================================
  Files          47       47           
  Lines        2090     2090           
  Branches      575      575           
=======================================
  Hits         1995     1995           
  Misses         32       32           
  Partials       63       63           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 65 rules

Grey Divider


Remediation recommended

1. Stale plugin version 🐞 Bug ≡ Correctness
Description
The newly added lhm.plugin.json hardcodes version "3.3.0" while the repo’s current package/server
version is "3.4.0", creating inconsistent metadata for any tooling/registry that reads this plugin
manifest.
This drift is likely to cause incorrect version display/update behavior unless the version is
intentionally independent and documented.
Code

lhm.plugin.json[R9-12]

+	"identifier": "chrisdoc-hevy-mcp",
+	"name": "Hevy MCP Server",
+	"tags": ["hevy", "fitness", "workouts", "health", "mcp"],
+	"version": "3.3.0"
Relevance

⭐⭐⭐ High

Team enforces manifest/package version sync; PR574 added drift check/sync tooling and accepted
related review suggestions.

PR-#574

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The new plugin manifest declares version 3.3.0, while the repository’s canonical version values used
for publishing/manifesting are already 3.4.0 in package.json and server.json, indicating drift
introduced by this PR.

lhm.plugin.json[1-13]
package.json[1-4]
server.json[1-16]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`lhm.plugin.json` declares `"version": "3.3.0"`, but the repository’s current version is `3.4.0` (as reflected in `package.json` and `server.json`). This creates inconsistent version metadata.

### Issue Context
This PR introduces `lhm.plugin.json` as a new manifest file; if it is consumed by external registries (e.g., LobeHub) it should reflect the current released version, or else explicitly document why it differs.

### Fix Focus Areas
- lhm.plugin.json[9-12]
- package.json[1-4]
- server.json[1-16]

### Suggested fix
- Update `lhm.plugin.json` `version` to `3.4.0` to match `package.json`/`server.json`.
- If the version is meant to be independent, add a short comment in project docs explaining the divergence and how/when it should be updated.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

Comment thread lhm.plugin.json
"description": "Manage Hevy workouts, routines, folders, body measurements, and exercise templates from MCP clients through the Hevy API.",
"homepage": "https://github.com/chrisdoc/hevy-mcp",
"icon": "https://github.com/chrisdoc.png",
"identifier": "chrisdoc-hevy-mcp",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Stale plugin version 🐞 Bug ≡ Correctness

The newly added lhm.plugin.json hardcodes version "3.3.0" while the repo’s current package/server
version is "3.4.0", creating inconsistent metadata for any tooling/registry that reads this plugin
manifest.
This drift is likely to cause incorrect version display/update behavior unless the version is
intentionally independent and documented.
Agent Prompt
### Issue description
`lhm.plugin.json` declares `"version": "3.3.0"`, but the repository’s current version is `3.4.0` (as reflected in `package.json` and `server.json`). This creates inconsistent version metadata.

### Issue Context
This PR introduces `lhm.plugin.json` as a new manifest file; if it is consumed by external registries (e.g., LobeHub) it should reflect the current released version, or else explicitly document why it differs.

### Fix Focus Areas
- lhm.plugin.json[9-12]
- package.json[1-4]
- server.json[1-16]

### Suggested fix
- Update `lhm.plugin.json` `version` to `3.4.0` to match `package.json`/`server.json`.
- If the version is meant to be independent, add a short comment in project docs explaining the divergence and how/when it should be updated.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant