Connecte un client IA aux compétences, plugins, workflows et connexions de votre organisation OpenWork via une URL OAuth unique.
Aussi connu sous different-ai/openwork, openwork
- Étoiles
- 24 524
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 1.0.0
- Dernier commit
- 14 nov. 2026
- Licence
- —
Qu'est-ce que OpenWork MCP ?
Connecte un client IA aux compétences, plugins, workflows et connexions de votre organisation OpenWork via une URL OAuth unique.
Résumé généré à partir du README du projet
À propos du MCP server OpenWork
L'OpenWork MCP Gateway permet de connecter un client IA aux outils et workflows internes de votre organisation. Il agit comme un plan de contrôle centralisé qui permet aux agents d'interagir avec les compétences, plugins et connexions spécifiques de votre organisation via une URL OAuth unique. Cette configuration est conçue pour les développeurs et les organisations qui doivent gérer la manière dont les agents IA accèdent à des ressources protégées au sein d'un environnement structuré.
Le serveur gère des données organisationnelles complexes, notamment les appartenances des utilisateurs, les structures d'équipe et l'activité des travailleurs. Il utilise une architecture basée sur Hono pour fournir des surfaces de routage organisées pour l'authentification, la gestion de l'organisation et le provisionnement SCIM. Les administrateurs peuvent contrôler l'accès en approuvant des origines web HTTPS spécifiques, avec une limite allant jusqu'à 20 origines approuvées par organisation.
Pour l'observabilité, le système prend en charge le logging JSON structuré, OpenTelemetry pour le traçage distribué et les métriques, ou Sentry pour le suivi des erreurs. Il utilise un cache de type read-through basé sur Redis pour optimiser les performances lors de requêtes fréquentes, telles que la validation de session et la recherche d'appartenance. La passerelle garantit la sécurité en masquant les valeurs sensibles d'autorisation et de corps de requête dans la télémétrie, et en imposant une validation TypeID stricte pour tous les identifiants.
Ce que vous pouvez faire avec
- 1Surveiller l'activité des travailleursLes développeurs peuvent utiliser la passerelle pour lister les travailleurs et surveiller leurs signaux d'activité (heartbeats).
- 2Provisionner des utilisateurs via SCIMAutomatisez l'adoption des utilisateurs et la gestion des appartenances au sein d'une organisation en utilisant les protocoles SCIM.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer OpenWork MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller OpenWork MCP dans Claude Code
$ claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agentInstaller OpenWork MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"openwork": {
"url": "https://api.openworklabs.com/mcp/agent"
}
}
}Installer OpenWork MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"openwork": {
"type": "http",
"url": "https://api.openworklabs.com/mcp/agent"
}
}
}Installer OpenWork MCP dans VS Code CLI
$ code --add-mcp '{"name":"openwork","type":"http","url":"https://api.openworklabs.com/mcp/agent"}'Installer OpenWork MCP dans Codex
$ codex mcp add openwork --url https://api.openworklabs.com/mcp/agentInstaller OpenWork MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.openwork] url = "https://api.openworklabs.com/mcp/agent"
Installer OpenWork MCP dans Gemini CLI
$ gemini mcp add -s user --transport http openwork https://api.openworklabs.com/mcp/agentInstaller OpenWork MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"openwork": {
"url": "https://api.openworklabs.com/mcp/agent",
"type": "http"
}
}
}Vérifications automatisées
Exécuté le 12 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications · Ce qu'il faut corriger pour gagner des points
- Dépôt source lié et accessibleRéussi
- Licence open source (OSI)No licenseFaille
- Commit ou version publiée au cours de l'année écouléeRéussi
- Nom du package non proche d'un package populaireNon vérifié
- L'endpoint distant utilise HTTPSRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Aucune instruction cachée destinée au modèleRéussi
- Aucun avis critique dans le package ou ses dépendancesNon vérifié
README
Voir sur GitHubDen API
Hono-based Den control plane implementation (den-api, formerly den-controller).
This package is the active Den control plane implementation.
It carries the full migrated Den API route surface in a foldered Hono structure so agents can navigate one area at a time without scanning the whole service.
Quick start
pnpm --filter @openwork-ee/den-api dev:local
Local demo org seed
With a local Den MySQL database running, seed a demo organization:
pnpm --filter @openwork-ee/den-api seed:demo-org
This creates Acme Robotics with demo users, teams, pending invites, and an imported Anthropic Knowledge Work Plugins marketplace. It is guarded by OPENWORK_DEV_MODE=1, defaults to the local Den DB URL, and does not create workers or active external integrations.
Default owner login: alex@acme.test / OpenWorkDemo123!.
Observability
DEN_OBSERVABILITY_BACKEND selects one backend: none, otel, or sentry.
none(default): structured JSON logs are written to stdout.otel: initializes the OpenTelemetry Node SDK before Hono/DB imports, exports OTLP HTTP/protobuf traces, metrics, and logs from standardOTEL_*variables, and uses@hono/otelfor normalized request spans/metrics without inbound HTTP auto-instrumentation.sentry: initializes@sentry/hono/nodebefore app imports and uses the official Hono middleware for errors/tracing/Sentry Logs. Do not combine it with the OTEL backend.
The request access log records request id, method, normalized route, status, duration and the number of database statements the request issued (db_queries, a count only), and omits health/readiness noise. Health/readiness requests also skip den-api's Hono observability middleware. Authorization, cookie, body, and query values are redacted from app telemetry. OTEL_SERVICE_NAME overrides the default den-api service name. Daytona's own OTEL bootstrap remains disabled; do not set Daytona OTEL enable variables from den-api.
Builds generate source maps. Sentry source maps are uploaded only when DEN_OBSERVABILITY_BACKEND=sentry and SENTRY_AUTH_TOKEN, SENTRY_ORG, SENTRY_PROJECT, and SENTRY_RELEASE are present; SENTRY_DIST is passed through when set. The auth token must stay in secret storage and is never written to env examples or logs.
Approved web origins
Organization owners and admins approve self-hosted OpenWork Web instances in the Den dashboard under Org settings → Approved web origins (/v1/org/web-origins). Each entry is an exact HTTPS origin — scheme, host, and optional port, with no path, query, fragment, credentials, or wildcard — and an organization can approve up to 20. An approved origin can receive web sign-in handoffs back to /signin only while that organization is active, and is allowed for credentialed browser requests to Den API. Handoff approval is checked on every request; CORS approval is cached per process and takes effect within about 30 seconds on every Den API replica. If DEN_CORS_HANDLED_BY_EDGE=true, the edge must also allow the same exact origin and the Authorization preflight.
Current routes
GET /->302 https://openworklabs.comGET /health- Better Auth mount at
/api/auth/* - desktop handoff routes under
/v1/auth/* - current user routes under
/v1/me* - organization routes under
/v1/orgs* - active-organization SCIM management routes under
/v1/scim* - admin routes under
/v1/admin* - worker list, delete, and activity heartbeat routes under
/v1/workers*(OpenWork Web instances are worker rows; their lifecycle lives under/v1/cloud/*)
Folder map
src/routes/auth/: Better Auth mount + desktop handoff endpointssrc/routes/me/: current user and current user's org resolution routessrc/routes/org/: organization CRUD-ish surfaces, split by areasrc/routes/admin/: admin-only reporting endpointssrc/routes/workers/: worker list, delete, and activity heartbeat endpointssrc/middleware/: reusable Hono middleware for auth context, org context, teams, and validationsrc/cache.ts: shared Redis-backed read-through cache. Add expensive read helpers here, keyed ascache:${cacheParent}:${cacheChild}:${id}; for examplecache.auth.session(token)andcache.org.members(orgId). Redis is optional, so every helper must fall back to the DB loader.
Each major folder also has its own README.md so future agents can inspect one area in isolation.
Shared query cache
Use src/cache.ts for Den API read-through Redis caching. Do not create ad-hoc Redis calls in route handlers or domain modules.
Current public helpers:
const session = await cache.auth.session(token)
const members = await cache.org.members(orgId)
Cache key format:
cache:${cacheParent}:${cacheChild}:${id}
Example key:
cache:auth:session:<token>
cache:org:members:org_...
Rules for adding cache helpers:
- Add helpers under the exported
cachenamespace insrc/cache.ts. - Keep each helper as a read-through function: check Redis, run the DB loader on miss, write Redis, then return the loaded value.
- Redis is optional. Helpers must work when
DATABASE_REDIS_URLis unset. - Non-local Redis should use
rediss://. SetDATABASE_REDIS_ALLOW_INSECURE_INTERNAL=1only when theredis://endpoint is private, non-public, and restricted to a trusted internal network. - Use short TTLs unless invalidation is explicit and tested.
- Auth sessions are DB-authoritative and cached for at most one hour. Any session delete or identity-changing update must invalidate
cache.auth.deleteSession(token). - Do not add new security-critical cache helpers without explicit invalidation and tests.
- Prefer names that read like domain calls, for example
cache.auth.session(token)orcache.org.members(orgId).
SCIM existing-user adoption
The SCIM plugin in src/auth.ts requires existing membership in the connector's
organization before adopting an existing account. Its shouldLinkUser callback
also performs an uncached membership read by normalized user and organization
IDs with removed_at IS NULL. Better Auth 1.7.0-beta.10's built-in membership
lookup does not exclude removed rows, so both checks must remain enabled.
Invitations without a joined user, removed memberships, outside-org accounts,
and tokens without an organization cannot authorize adoption. No email-domain
exception applies. Successful adoption preserves the user ID and membership role;
the new-user provisioning path is unchanged.
The plugin evaluates this policy before its account-creation transaction. The fresh read excludes already-removed memberships, but does not serialize a concurrent removal with linking. Closing that race requires transactional policy support in the plugin; this callback is not an atomic membership lock.
Run the installed-plugin regression suite in its own Node process:
pnpm --filter @openwork-ee/den-api test:scim-existing-user-linking
It uses Better Auth's memory adapter and compiles the membership SQL without executing it. It does not import Den's full auth graph, start MySQL, configure OAuth, or require real credentials.
TypeID validation
- Shared Den TypeID validation lives in
ee/packages/utils/src/typeid.ts. - Use
typeId.schema("...")or the compatibility helpers likenormalizeDenTypeId("...", value)when an endpoint accepts or returns a Den TypeID. ee/apps/den-api/src/openapi.tsexposesdenTypeIdSchema(...)so path params, request bodies, and response fields all share the same validation rules and Swagger examples.- Swagger now documents Den IDs with their required prefix and fixed 26-character TypeID suffix, so invalid IDs fail request validation before route logic runs.
OpenAPI contract
packages/docs/openapi.jsonis an ignored build artifact generated bypnpm den:contractand linted withpnpm api:lint. CI generates OpenAPI/SDK from source and fails on generation/type errors, Spectral errors, or warnings above.spectral-baseline.json. Hosted docs read the same normalized public contract from/openapi.json?public=1;.github/workflows/refresh-api-docs.ymlrebuilds them once production serves a contract change.- Every route registration carries a
describeRoute()withsummary,tags,securityandresponses; conventions and documented exceptions are indocs/api-style.md.
Migration approach
- Keep
den-api(formerlyden-controller) as the source of truth for Den control-plane behavior. - Add endpoints in focused Hono route groups one surface at a time.
- Reuse shared middleware and Zod validators instead of duplicating request/session/org plumbing.
- Leave a short README in each route area when the structure changes so later agents can recover context fast.
Questions sur OpenWork MCP
Comment ajouter OpenWork MCP à Claude Code ?
Exécutez claude mcp add --transport http openwork https://api.openworklabs.com/mcp/agent dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter OpenWork MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Qui approuve les origines web autorisées à se connecter à une organisation ?
Les propriétaires et administrateurs de l'organisation approuvent les instances Web OpenWork auto-hébergées en tant qu'origines HTTPS exactes dans le tableau de bord.