Skip to content

[Draft] Add Embarko third-party MCP plugin - #919

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
add-embarko-mcp-plugin
Draft

cursor[bot] wants to merge 1 commit into
mainfrom
add-embarko-mcp-plugin

Conversation

@cursor

@cursor cursor Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Unreviewed submission. This plugin came from the plugin submission form and has not been reviewed. Do not merge until someone has checked the server and the listing.

Adds the Embarko (Walkover) remote MCP plugin under third_party/embarko/, following the PitchBook layout from #796.

Changes

  • third_party/embarko/mcp.json: embarko http server at the submitted URL, https://mcp.embarko.ai/mcp.
  • .cursor-plugin/plugin.json with "mcpServers": "./mcp.json" and category integrations.
  • README (install steps and the MCP block), CHANGELOG, LICENSE.
  • One row in the root README integrations table and one entry appended to .cursor-plugin/marketplace.json. .claude-plugin/marketplace.json is unchanged.

Submission

Testing instructions (as submitted)

Embarko by Walkover (hosting for apps built with AI)
Server: https://mcp.embarko.ai/mcp (OAuth)

Connect: grok.com/connectors → New Connector → Custom → paste the URL above
→ sign in with your Embarko account (free to create at embarko.ai).

Test 1 (deploy):
Prompt: "Deploy a one-page website with the heading 'Hello from Grok' to Embarko."
Expected: Grok deploys the site and returns a live link ending in .embarko.app. Opening the link shows the heading.

Test 2 (status):
Prompt: "Is that app live?"
Expected: Grok reports the app status as live.

In Cursor, install the plugin, finish the Embarko OAuth sign-in, then run the same two prompts.

Logo: no local file committed
The logo could not be downloaded. The submitted logo_url, embarko.ai/favicon.ico, www.embarko.ai and mcp.embarko.ai all failed the TLS handshake from the build VM, and the off-VM web fetcher blocks embarko.ai. The embarko-ai GitHub organization (owner of embarko-ai/skill, homepage embarko.ai) only has GitHub's default identicon, so I did not use it. The GitHub user embarko has no link to embarko.ai. No repository on GitHub contains embarko-icon. plugin.json therefore sets "logo" to the submitted absolute URL, https://embarko.ai/assets/embarko-icon.svg, which the plugin schema allows. Before merging, download that SVG (or a PNG of it) into third_party/embarko/assets/ and set "logo" to the relative path.

Not verified

  • I could not reach mcp.embarko.ai from the VM, so the OAuth flow and tool list have not been checked.
  • Embarko also publishes an agent skill at https://github.com/embarko-ai/skill. It is not included here because the submission is the remote MCP server.
  • Another automation run pushed an unrelated add-embarko-plugin branch for this same submission without opening a PR. I left it alone. This PR uses add-embarko-mcp-plugin.

Validation
node scripts/validate-plugins.mjs passes.

Open in Web View Automation 

Note

Medium Risk
Lists an unreviewed third-party OAuth MCP that can trigger deployments on an external host; trust and behavior depend entirely on Embarko’s remote server, which was not verified in this PR.

Overview
Adds Embarko (Walkover) as a new third-party integration so Cursor agents can deploy and host AI-built apps via Embarko’s hosted MCP.

The PR introduces third_party/embarko/ with the usual plugin bundle: .cursor-plugin/plugin.json (integrations category, mcpServers → ./mcp.json), an HTTP MCP entry at https://mcp.embarko.ai/mcp (OAuth), plus README, CHANGELOG, and LICENSE. It also registers embarko in the root .cursor-plugin/marketplace.json and the README integrations table.

The manifest uses a remote logo URL (https://embarko.ai/assets/embarko-icon.svg) because no local asset was committed. The PR is marked as an unreviewed submission; the hosted MCP endpoint was not verified in the authoring environment.

Reviewed by Cursor Bugbot for commit 1c3ec83. Bugbot is set up for automated code reviews on this repo. Configure here.

Co-authored-by: Danny Jiang <djiang-jq@users.noreply.github.com>
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