2026-09-02 01:05:41 +08:00
commit 04bac1f6e2
2200 changed files with 489415 additions and 0 deletions
@@ -0,0 +1,22 @@
# OpenWork Connect Agent Plugin
This directory is the portable OpenWork Connect package for the published
Agent Plugins 1.0.0 specification. Install or copy the complete directory
through an Agent Plugins-compatible client. The package installs:
- the remote OpenWork MCP endpoint;
- guidance for the `search_capabilities` and `execute_capability` workflow;
- no credentials or client-specific authentication configuration.
The MCP client discovers OpenWork OAuth from the endpoint and opens the normal
browser sign-in flow. Access remains scoped to the selected organization and
the signed-in member's grants.
The `streamable-http` entry does not pin an MCP wire version. OpenWork Connect
negotiates the stateless MCP 2026-07-28 protocol with current clients and keeps
the existing MCP 2025-11-25 compatibility path for clients that have not yet
migrated. No session identifier, token, or protocol-specific header is stored
in this package.
Agent Plugins does not standardize registries or installation UX. Distribution
of this directory is therefore client-specific.
@@ -0,0 +1,9 @@
{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
  "mcpServers": {
    "openwork": {
      "type": "streamable-http",
      "url": "https://api.openworklabs.com/mcp/agent"
    }
  }
}
@@ -0,0 +1,19 @@
{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "openwork-connect",
  "version": "1.0.0",
  "description": "Use the skills, MCP connections, and connected services assigned to you through OpenWork.",
  "author": {
    "name": "OpenWork",
    "url": "https://openworklabs.com"
  },
  "homepage": "https://openworklabs.com/docs/cloud/run-in-the-cloud/cloud-mcp",
  "repository": "https://github.com/different-ai/openwork",
  "license": "MIT",
  "keywords": [
    "openwork",
    "mcp",
    "agent-skills",
    "organization"
  ]
}
@@ -0,0 +1,27 @@
---
name: openwork-connect
description: Search and use the skills, MCP connections, and connected services available through the user's OpenWork organization.
---
# OpenWork Connect
Use the OpenWork MCP server when the user asks for an organizational skill,
shared MCP tool, connected service, or OpenWork Cloud operation.
## Workflow
1. Call `search_capabilities` with a short description of the outcome unless
   the exact capability name is already available in the current context.
2. Select an exact capability name from the search result.
3. Call `execute_capability` with that exact name and only the parameters
   required for the requested outcome.
4. If OpenWork returns a connection, authentication, permission, or admin
   setup state, relay that state and its next action accurately. Do not claim
   that an unavailable capability ran.
Search results reflect the signed-in member's organization, grants, teams, and
connection readiness. Do not infer access from a capability that was visible
in another organization or an earlier authorization context.
OpenWork Connect performs OAuth through the MCP client. Never request, embed,
or persist OpenWork access tokens in plugin files or chat content.