[cursor]

Unreviewed plugin submission. This PR was generated automatically from a submission form and has not been reviewed. Do not merge until someone has verified the publisher and tested the MCP server.

Submission

• Publisher handle: pengju
• Company: Pengju, LLC
• Contact: Ryan Yan support@litsource.net
• Website: https://litsource.net
• plugin_url: https://litsynth.ai/api/mcp (remote MCP server, used as-is)
• Listing targets: Grok Bot, Cursor

What's added

• third_party/pengju/mcp.json: HTTP MCP server pengju at https://litsynth.ai/api/mcp
• third_party/pengju/.cursor-plugin/plugin.json with "mcpServers": "./mcp.json" (same pattern as PitchBook, Add PitchBook third-party MCP plugin #796)
• third_party/pengju/README.md, LICENSE, assets/logo.svg
• One entry in .cursor-plugin/marketplace.json and one row in the root README integrations table. .claude-plugin/marketplace.json is unchanged.

Logo

The submitted logo_url (https://litsynth.ai/favicon.svg) could not be fetched from the build environment (TLS connection reset; litsynth.ai and litsource.net are both unreachable from here). The committed assets/logo.svg is the LitSynth mark from the publisher's own asset host, https://pengju-marketplace-assets.vercel.app/litsynth-marketplace.svg (index page titled "Pengju marketplace assets"). Reviewers may want to confirm it matches the submitted favicon.

Note

An earlier submission from the same publisher handle (LitSource, https://litsource.net/mcp) was pushed to branch add-pengju-plugin but never got a PR. It also uses third_party/pengju/, so the two conflict. If both products should be listed, one of them will need a different plugin name.

Testing instructions (from the submitter)

1. Add MCP https://litsynth.ai/api/mcp (public read tools work without sign-in).
2. Prompt: Call litsynth_get_release_info and report the running version.
3. Prompt: List recent releases with litsynth_list_releases.
4. For generation: create a token in Settings -> Security with generate scope, authenticate, then litsynth_list_review_runs -> prepare -> generate (uses credits).

Validation

node scripts/validate-plugins.mjs passes.

  

---

Note

Medium Risk
Unreviewed third-party submission that lists an external MCP endpoint and documents account tokens for generation; repo changes are additive but merge should wait on publisher and server verification.

Overview
Adds a new LitSynth third-party integration (pengju) that wires Cursor to Pengju’s hosted HTTP MCP at https://litsynth.ai/api/mcp, following the same manifest + ./mcp.json pattern as other remote MCP plugins.

The new third_party/pengju/ bundle includes plugin metadata, README (install via Plugins or /add-plugin pengju, public read tools vs token-backed review generation), MIT license, and a committed assets/logo.svg (fallback because the submitted favicon URL was unreachable in CI). Marketplace and root README integrations table each gain one listing row for LitSynth / literature-review tooling with traceable citations.

^{Reviewed by Cursor Bugbot for commit 640cf07. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but it could not run because the Cursor GitHub App does not have access to this repository. If the app is installed on your organization with "selected repositories", make sure this repository is included in the selection.}

^{Reviewed by Cursor Bugbot for commit 640cf07. Configure here.}

[cursor]

Missing Cursor version requirement

Medium Severity · Potential Edge Case

plugin.json omits minClientVersions, so this HTTP MCP plugin can be installed on Cursor builds that cannot run plugin-hosted HTTP MCP. Other HTTP MCP integrations in this repo, including the PitchBook pattern this PR cites, declare a cursor floor of 3.13.0.

 

^{Reviewed by Cursor Bugbot for commit 640cf07. Configure here.}