Skip to content

feat(third_party): add Jobber plugin - #5

Draft
djiang-jq wants to merge 1 commit into
mainfrom
cursor/add-jobber-plugin-e49d
Draft

djiang-jq wants to merge 1 commit into
mainfrom
cursor/add-jobber-plugin-e49d

Conversation

@djiang-jq

Copy link
Copy Markdown
Owner

Adds Jobber as a URL-only connector to Jobber's hosted MCP server, following the same shape as the other recent third_party MCP plugins (Plaud, Buffer, PostHog).

Submission details:

Field Value
Display name Jobber
Organization jobber
Contact [email protected]
Server URL https://mcp.getjobber.com/mcp
Website https://www.getjobber.com/

What's here

  • third_party/jobber/.cursor-plugin/plugin.json — manifest (integrations category, minClientVersions.cursor 3.13.0, Cursor as author per repo convention).
  • third_party/jobber/mcp.json — type: http pointing at https://mcp.getjobber.com/mcp, with "placement": "server" so Grok Bot dials it through the hosted MCP path (without it the row stays UNDECIDED and never shows a connect card).
  • README.md, CHANGELOG.md, LICENSE, and a 192×192 assets/logo.png.
  • Registered in .cursor-plugin/marketplace.json and the root README.md plugin table.

node scripts/validate-plugins.mjs passes.

Logo

The Brandfolder link in the submission is a wide lockup (mark plus wordmark) and the host is outside this environment's network allowlist, so the asset was rebuilt as a square tile instead: Jobber's brandmark in white on Jobber green (#7DB00E), 192×192, matching the mark in Jobber's own logo SVG (GetJobber/Jobber-AppTemplate-React) and Jobber's favicon. Happy to swap in the exact Brandfolder export if Jobber prefers a different treatment.

Needs a reviewer with network access

mcp.getjobber.com and getjobber.com are both blocked from this environment, so the following could not be exercised and should be checked before approval:

  • The OAuth connect flow (PKCE + dynamic client registration against every Cursor redirect set, including Grok Bot mobile). The README describes OAuth sign-in with no API key, which is the expected shape for a hosted /mcp endpoint but is unverified here.
  • The live tool list. The README deliberately describes capabilities in Jobber's own product terms (clients, properties, requests, quotes, jobs, visits, invoices, payments) and names no tools, so nothing has to be corrected if the server's schemas differ.
  • Whether Jobber publishes MCP-specific docs to use as homepage; it currently points at https://www.getjobber.com/.
Open in Web Open in Cursor 

URL-only connector to Jobber's hosted MCP server at
https://mcp.getjobber.com/mcp, with placement: server so Grok Bot dials
it through the hosted MCP path.

Submitted by [email protected] (Jobber).

Co-authored-by: Danny Jiang <[email protected]>
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.

2 participants