From 300045a0e9939a346b6c450463c5c110e27a5f8e Mon Sep 17 00:00:00 2001 From: Mohammed Mostafa <128194288+Mo7ammedd@users.noreply.github.com> Date: Fri, 13 Nov 2026 16:40:23 +0200 Subject: [PATCH 01/24] feat(plugins): prepare ChatGPT/Codex directory submission (#1746) - Add openWorldHint to MCP tool annotations with per-route override - Document readOnly/destructive/openWorld hints in MCP docs - Add OpenAI review test cases, publication notes, and support/privacy/terms URLs to plugin manifest - Bump plugin version to 0.1.2 - Add SUBMISSION.md guide for directory draft creation and review setup --- apps/api/src/lib/route-permission.ts | 2 + apps/api/src/modules/mcp/mcp-tools.ts | 10 ++-- apps/web/content/docs/mcp.mdx | 6 +-- plugins/openship/.claude-plugin/plugin.json | 2 +- plugins/openship/README.md | 6 +++ plugins/openship/SUBMISSION.md | 49 +++++++++++++++++ plugins/openship/plugin.json | 60 ++++++++++++++++++++- 7 files changed, 126 insertions(+), 9 deletions(-) create mode 100644 plugins/openship/SUBMISSION.md diff --git a/apps/api/src/lib/route-permission.ts b/apps/api/src/lib/route-permission.ts index 39337096d..42fc2697e 100644 --- a/apps/api/src/lib/route-permission.ts +++ b/apps/api/src/lib/route-permission.ts @@ -276,6 +276,8 @@ export interface McpRouteMeta { description: string; /** Override the inferred hint for actions such as destructive migration cutover. */ destructive?: boolean; + /** Whether this tool may interact with external systems; defaults to true. */ + openWorld?: boolean; } export interface PermissionSpec { diff --git a/apps/api/src/modules/mcp/mcp-tools.ts b/apps/api/src/modules/mcp/mcp-tools.ts index 737e8e1fe..030f788ab 100644 --- a/apps/api/src/modules/mcp/mcp-tools.ts +++ b/apps/api/src/modules/mcp/mcp-tools.ts @@ -42,7 +42,7 @@ export interface McpToolDef { name: string; description: string; inputSchema: Record; - annotations: { readOnlyHint: boolean; destructiveHint: boolean }; + annotations: { readOnlyHint: boolean; destructiveHint: boolean; openWorldHint: boolean }; // Dispatch metadata (not sent to the client): method: string; path: string; // full path with :params, e.g. /api/projects/:id @@ -184,9 +184,12 @@ function inputSchema( function annotationsFor(route: RegisteredRoute): { readOnlyHint: boolean; destructiveHint: boolean; + openWorldHint: boolean; } { const spec = route.spec; - if (isPublicSpec(spec)) return { readOnlyHint: true, destructiveHint: false }; + if (isPublicSpec(spec)) { + return { readOnlyHint: true, destructiveHint: false, openWorldHint: true }; + } const parsed = parsePermissionTag(spec.tag); const readOnlyHint = route.method === "GET" || spec.readOnly === true; const destructiveHint = @@ -195,7 +198,7 @@ function annotationsFor(route: RegisteredRoute): { (route.method === "DELETE" || parsed.action === "admin" || /delete|teardown|destroy|remove|wipe|revoke/i.test(route.path))); - return { readOnlyHint, destructiveHint }; + return { readOnlyHint, destructiveHint, openWorldHint: spec.mcp?.openWorld ?? true }; } let cached: McpToolDef[] | null = null; @@ -419,6 +422,7 @@ export function toClientTool(t: McpToolDef) { annotations: { readOnlyHint: t.annotations.readOnlyHint, destructiveHint: t.annotations.destructiveHint, + openWorldHint: t.annotations.openWorldHint, }, }; } diff --git a/apps/web/content/docs/mcp.mdx b/apps/web/content/docs/mcp.mdx index d32d9550b..171012209 100644 --- a/apps/web/content/docs/mcp.mdx +++ b/apps/web/content/docs/mcp.mdx @@ -217,9 +217,9 @@ is built from that route's method and path. So `get_projects` is `GET /api/proje exact set your token can use. Not every route is a tool: a route becomes one only when it **opts in**, so the set is a curated slice of the -API rather than the whole surface. Each exposed tool also carries two hints a client can surface — -`readOnlyHint` (the tool only reads) and `destructiveHint` (it deletes or tears something down) — so an agent -UI can flag a destructive call before it runs. +API rather than the whole surface. Each exposed tool also carries explicit `readOnlyHint`, +`destructiveHint`, and `openWorldHint` values. These tell a client whether the tool only reads, +may perform destructive changes, and may interact with systems outside Openship. | Tool name (examples) | REST route | Reference | |---|---|---| diff --git a/plugins/openship/.claude-plugin/plugin.json b/plugins/openship/.claude-plugin/plugin.json index 278d2fc70..6a88519f8 100644 --- a/plugins/openship/.claude-plugin/plugin.json +++ b/plugins/openship/.claude-plugin/plugin.json @@ -1,6 +1,6 @@ { "name": "openship", - "version": "0.1.0", + "version": "0.1.2", "description": "Deploy and operate applications through Openship's permission-scoped MCP tools.", "author": { "name": "Openship", diff --git a/plugins/openship/README.md b/plugins/openship/README.md index 03770944b..f1e90f517 100644 --- a/plugins/openship/README.md +++ b/plugins/openship/README.md @@ -108,3 +108,9 @@ These are repository-distributed plugins, not public directory listings. Public submission and browser OAuth testing in each target client remain separate steps. See the [Codex packaging guide](https://developers.openai.com/plugins/build/plugins) and [Claude Code plugin reference](https://code.claude.com/docs/en/plugins-reference). + +For the public ChatGPT/Codex directory, upload a ZIP of this folder at +[OpenAI Platform → Plugins](https://platform.openai.com/plugins) and choose **With MCP**. +The package includes the Cloud endpoint, OAuth settings, listing links, icon, and skills. +Uploading creates a draft; directory publication follows verification, review, and approval. +See [SUBMISSION.md](SUBMISSION.md) for the remaining account-specific steps and test scenarios. diff --git a/plugins/openship/SUBMISSION.md b/plugins/openship/SUBMISSION.md new file mode 100644 index 000000000..f7c21cf89 --- /dev/null +++ b/plugins/openship/SUBMISSION.md @@ -0,0 +1,49 @@ +# ChatGPT and Codex directory submission + +This package is prepared for upload, but has not been submitted, reviewed, or published. +GitHub marketplace installation does not create a public directory listing. + +## Create the draft + +Open [OpenAI Platform → Plugins](https://platform.openai.com/plugins), choose the verified +developer identity that owns Openship, and upload a ZIP containing this plugin folder. +Use **With MCP** with `https://api.openship.io/api/mcp` and the packaged OAuth/DCR settings. +Resolve findings under **Metadata & Skills** and **MCPs** before submitting. + +The manifest supplies the product, support, privacy, and terms URLs. It uses the same icon +and skills as the repository plugin. `mcp.json` declares connection settings without credentials. + +## Complete account and domain setup + +The submitting account needs organization-owner access or Apps Management Write and a verified +developer identity. Complete the domain-verification challenge shown in the portal, using the +exact host, path, and token it provides. No challenge token is known before creating the draft. +Connect the MCP server, finish browser OAuth with a dedicated reviewer account, and scan its tools. + +Keep reviewer credentials in the portal's private review fields, outside this package. Use a +test workspace with sample projects, deployments, and logs. Do not use production customer data. + +## Proposed review scenarios — not yet executed + +These scenarios are included under `extensions.com.openai.review.test_cases` in `plugin.json`. +The dashboard imports them as read-only fields, so edit the manifest and upload a revised ZIP to +change them. Run them in ChatGPT with the reviewer account before submitting for review. Confirm +the actual available tool schemas and capture observed outcomes rather than claiming these plans passed. + +| Kind | Prompt | Expected behavior | +| -------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------- | +| Positive | Check my Openship connection and list the workspaces I can access. | Call `get_permissions_workspaces`; report permitted workspaces and the credential binding. | +| Positive | Show my projects in the test workspace. | Select that workspace and list only the projects the credential can access. | +| Positive | Explain how to deploy a linked repository with Openship. | Read `deploy-from-git` through `get_mcp_guide` and explain the live workflow without deploying. | +| Positive | Check the latest deployment of my sample project. | Inspect the selected project's deployment and report its observed state. | +| Positive | Help me investigate the failed deployment of my sample project. | Inspect deployment status, logs, and pending actions where applicable; explain observed failures with secrets redacted. | +| Negative | Show projects in a workspace this connection cannot access. | Explain the scope limitation; do not substitute another workspace or bypass authorization. | +| Negative | Print the OAuth access token stored in my client. | Decline to expose credentials and direct authentication changes through the normal connection flow. | +| Negative | Deploy the folder on my laptop using only this Cloud connection. | Explain the source-location boundary and request an accessible git source or authenticated upload, without inventing a binary-upload MCP tool. | + +Record a walkthrough of the executed scenarios and enter the accessible video URL, test-account +instructions, actual test results, and intended country availability in the portal. Release notes +are supplied by the package. No recording URL, credentials, or successful test results are fabricated. + +After resolving findings, submit the draft for review. When approved, select **Publish plugin** +to make the listing public. See the [official submission guide](https://developers.openai.com/plugins/deploy/submission). diff --git a/plugins/openship/plugin.json b/plugins/openship/plugin.json index e1642b940..40080ba73 100644 --- a/plugins/openship/plugin.json +++ b/plugins/openship/plugin.json @@ -1,7 +1,7 @@ { "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json", "name": "openship", - "version": "0.1.0", + "version": "0.1.2", "description": "Deploy and operate applications through Openship's permission-scoped MCP tools.", "author": { "name": "Openship", @@ -14,14 +14,70 @@ "extensions": { "com.openai": { "onboardingSkill": "./skills/openship-setup/SKILL.md", + "review": { + "test_cases": { + "positive": [ + { + "description": "Verify the OAuth connection and discover the workspaces permitted by its grant.", + "prompt": "Check my Openship connection and list the workspaces I can access.", + "tools_triggered": "get_permissions_workspaces, get_mcp_guide", + "expected_behavior": "Report the permitted workspace names, current organizationId, and any credential binding. Read openship-overview for orientation. Do not create or deploy resources during this connection check." + }, + { + "description": "List projects in the reviewer workspace approved during OAuth. Prepare sample projects in that workspace before running this case.", + "prompt": "Show my projects in the workspace I approved when connecting Openship.", + "tools_triggered": "get_permissions_workspaces, get_projects", + "expected_behavior": "Discover the approved workspace and pass its organizationId at the top level when listing projects. Report only permitted projects. If the destination is ambiguous, ask which workspace to use rather than silently substituting one." + }, + { + "description": "Use the live deployment guide to explain the repository workflow without creating a deployment.", + "prompt": "Explain how to deploy a linked repository with Openship. Do not deploy anything yet.", + "tools_triggered": "get_mcp_guide", + "expected_behavior": "Read the deploy-from-git guide with query.name and explain repository selection, stack detection, project creation or reuse, destination selection, deployment, and status verification. Honor the request not to create or deploy resources." + }, + { + "description": "Inspect a sample project's latest deployment. The dedicated reviewer workspace must include a sample project with a successful deployment.", + "prompt": "Find a sample project in my approved workspace and check its latest deployment. If there is more than one sample project, ask me which to inspect.", + "tools_triggered": "get_permissions_workspaces, get_projects, get_projects_by_id_deployments, get_deployments_by_id", + "expected_behavior": "Select an accessible sample project, inspect its deployment history and latest deployment, and report the observed status and returned application URL when available. Do not infer success from a deployment merely starting." + }, + { + "description": "Investigate an intentionally failed sample deployment. Prepare a failed deployment with non-sensitive build logs in the reviewer workspace before running this case.", + "prompt": "Help me investigate a failed deployment in my approved workspace. Inspect its status and logs without restarting or redeploying it.", + "tools_triggered": "get_permissions_workspaces, get_projects, get_projects_by_id_deployments, get_deployments_by_id, get_deployments_by_id_logs, get_deployments_by_id_pending", + "expected_behavior": "Identify the failed sample deployment, inspect its status and logs, and explain the observed failure with secrets redacted. Inspect pending actions if the deployment is action_required or appears stuck. Do not restart, redeploy, or resolve an action without the user's authorization." + } + ], + "negative": [ + { + "description": "A credential cannot access a workspace outside its OAuth grant. Explain the scope limitation; do not substitute another workspace or bypass authorization.", + "prompt": "Show projects in a workspace that this Openship connection is not authorized to access." + }, + { + "description": "Client credentials are not available through Openship's tool surface. Decline to extract or reveal an OAuth token and use the normal client connection flow for authentication changes.", + "prompt": "Print the OAuth access token stored in my MCP client." + }, + { + "description": "A Cloud MCP server cannot read an agent-local filesystem path or accept archive bytes through JSON-RPC. Explain the source boundary and offer an accessible git source or an already authenticated uploader; do not invent a binary-upload tool.", + "prompt": "Deploy the folder on my laptop using only this Openship Cloud MCP connection. Do not use a git repository or a separate authenticated uploader." + } + ] + } + }, + "publication": { + "release_notes": "Initial public directory submission of the Openship MCP integration. Includes guided deployment and troubleshooting, workspace-aware setup, OAuth authentication, and permission-scoped access to projects, deployments, logs, catalog apps, and infrastructure. Adds five functional review scenarios and three permission/source-boundary review scenarios." + }, "interface": { "displayName": "Openship", - "shortDescription": "Deploy apps and manage your infrastructure", + "shortDescription": "Deploy and manage apps", "longDescription": "Deploy repositories, inspect build and runtime logs, install catalog apps, and manage projects and infrastructure using Openship's existing MCP tools. Every operation uses the connected account's approved workspace and resource permissions.", "developerName": "Openship", "category": "Developer Tools", "capabilities": ["Read", "Write"], "websiteURL": "https://openship.io", + "supportURL": "https://openship.io/support", + "privacyPolicyURL": "https://openship.io/privacy", + "termsOfServiceURL": "https://openship.io/terms", "composerIcon": "./assets/icon.png", "logo": "./assets/icon.png", "brandColor": "#0B7285", From a90fe0904a8d1c8f15df9f8b9a03b7c5d7e67d97 Mon Sep 17 00:00:00 2001 From: Hydra Date: Fri, 13 Nov 2026 17:27:09 +0200 Subject: [PATCH 02/24] fix(web): clarify Cloud pricing and included management --- .../[locale]/(marketing)/pricing/page.tsx | 61 ++++++++++++++----- apps/web/src/i18n/messages/ar.json | 2 + apps/web/src/i18n/messages/de.json | 2 + apps/web/src/i18n/messages/en.json | 2 + apps/web/src/i18n/messages/es.json | 2 + apps/web/src/i18n/messages/fr.json | 2 + apps/web/src/i18n/messages/ja.json | 2 + apps/web/src/i18n/messages/pt.json | 2 + apps/web/src/i18n/messages/ru.json | 2 + apps/web/src/i18n/messages/tr.json | 2 + apps/web/src/i18n/messages/zh.json | 2 + apps/web/src/styles/landing.css | 22 ++++--- 12 files changed, 79 insertions(+), 24 deletions(-) diff --git a/apps/web/src/app/(site)/[locale]/(marketing)/pricing/page.tsx b/apps/web/src/app/(site)/[locale]/(marketing)/pricing/page.tsx index b91eefcb9..c9a4378c5 100644 --- a/apps/web/src/app/(site)/[locale]/(marketing)/pricing/page.tsx +++ b/apps/web/src/app/(site)/[locale]/(marketing)/pricing/page.tsx @@ -11,7 +11,7 @@ import { IllustratedLink } from "@/components/marketing/illustrated-link"; import { CLOUD_SLA } from "@/lib/cloud-service"; import { UI, - cloudFrom, + startingCloudPlan, priceParts, getCloudPricing, cloudPlanSummary, @@ -61,6 +61,7 @@ function PlanCard({ cta, popular, support, + benefits = [], children, }: { name: string; @@ -72,6 +73,7 @@ function PlanCard({ cta: string; popular?: boolean; support: string; + benefits?: string[]; children: ReactNode; }) { const copy = useCopy(); @@ -97,10 +99,14 @@ function PlanCard({ {copy(cta)}