@0xmaxma/claude-gateway 1.8.7 → 1.8.9

package/dist/api/connectors-router.d.ts

@@ -0,0 +1,50 @@
+import { Router } from 'express';
+import { ApiKey } from '../types';
+import { type CustomConnectorsStore } from '../connectors/custom-connectors-store';
+import type { AgentRunner } from '../agent/runner';
+/**
+ * Connector management API. The gateway acts as connector registry + secret manager
+ * + config injector: connecting a connector stores its secret in mcp-token.env —
+ * that store alone is authoritative for "connected" (see resolve.ts's
+ * listConnectorStatus). The actual MCP server is injected into each session by
+ * SessionProcess (see resolveEnabledConnectors).
+ *
+ * Routes (mounted under /api):
+ *   GET    /v1/connectors                    — every connector, with connected state
+ *   GET    /v1/connectors/:id/status         — connected boolean (for polling)
+ *   POST   /v1/connectors/:id/connect        — store a secret (admin) into a
+ *                                              single-secret customConnectors entry
+ *                                              (e.g. reconnecting a paste-token
+ *                                              connector after DELETE
+ *                                              soft-disconnected it) — see the handler
+ *   POST   /v1/connectors/:id/oauth/receive  — store a pushed access_token (admin);
+ *                                              always writes credentialOwner 'external'
+ *   DELETE /v1/connectors/:id                — clear a secret (admin); a 'static' or
+ *                                              'gateway' connector keeps its
+ *                                              entry (config/label intact, just
+ *                                              disconnected), a 'none' or 'external'
+ *                                              one is removed outright — see the handler below
+ *   POST   /v1/connectors/custom             — add a user-pasted connector (admin)
+ *
+ * (Removal of a custom connector is NOT a separate route — it's the same
+ * DELETE /v1/connectors/:id above. See the note at the bottom of this file for
+ * why the old dedicated /custom/:id route was retired.)
+ *
+ * Externally-owned connectors (Gmail/Drive/Calendar) never do the actual OAuth
+ * dance here — an external control plane the deployer runs owns the
+ * client_secret, the token exchange, and the refresh loop (this gateway runs
+ * inside the user's own VM, reachable by that user's own shell/SSH, so a
+ * shared client_secret can't live here safely — see ConnectorCredentialOwner's
+ * doc comment). That control plane pushes the resulting short-lived
+ * access_token here via /oauth/receive, over the internal network,
+ * authenticated the same way any other admin API caller is. A connector this
+ * gateway signs in for itself is 'gateway' instead, and lives in
+ * oauth-connectors-router.ts.
+ *
+ * `agents` (all live AgentRunners) is what lets a route that changes a connector's
+ * secrets restart the sessions already using it — every route works without it
+ * (e.g. in tests), it just leaves running sessions on their stale MCP config
+ * until they next respawn on their own.
+ */
+export declare function createConnectorsRouter(apiKeys?: ApiKey[], configPath?: string, agents?: Map<string, AgentRunner>, customConnectorsStore?: CustomConnectorsStore): Router;
+//# sourceMappingURL=connectors-router.d.ts.map

package/dist/api/connectors-router.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"connectors-router.d.ts","sourceRoot":"","sources":["../../src/api/connectors-router.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,EAAmC,MAAM,SAAS,CAAC;AAClE,OAAO,EAAE,MAAM,EAAwB,MAAM,UAAU,CAAC;AAmBxD,OAAO,EAA+B,KAAK,qBAAqB,EAAE,MAAM,uCAAuC,CAAC;AAEhH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,iBAAiB,CAAC;AAInD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2CG;AACH,wBAAgB,sBAAsB,CACpC,OAAO,CAAC,EAAE,MAAM,EAAE,EAClB,UAAU,CAAC,EAAE,MAAM,EACnB,MAAM,CAAC,EAAE,GAAG,CAAC,MAAM,EAAE,WAAW,CAAC,EACjC,qBAAqB,CAAC,EAAE,qBAAqB,GAC5C,MAAM,CAgoBR"}