Consider adding official Kling AI regional MCP integration
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 74/100
Direzione di ricerca
Inizia leggendo integrations/catalog.schema.json e una voce esistente in integrations/catalog/ per copiare la forma prevista; il file di destinazione è integrations/catalog/kling-ai.json. Esegui npm run build:integrations per rigenerare integrations/catalog-index.js, poi i test dello schema e di sincronizzazione in tests/test_catalog_schema.py, tests/test_catalogs.py e tests/test_integration_catalog_in_sync.py. Fatto significa che questi test passano, una seconda build non produce alcun diff e le due opzioni di connessione MCP riportano i metadati OAuth elencati nei criteri di accettazione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Kling AI provides hosted, OAuth-backed MCP connections that let OpenHands users access Kling image and video creation from the agent. Could the integration catalog consider an official entry with separate Global and China connection options?
- Global endpoint: https://kling.ai/mcp/plugin
- China endpoint: https://klingai.com/mcp/plugin
- Official setup guide: https://kling.ai/app/mcp/guide
- Global plugin and CLI packages: https://www.npmjs.com/package/@klingai/plugin-global and https://www.npmjs.com/package/@klingai/cli-global
- China plugin and CLI packages: https://www.npmjs.com/package/@klingai/plugin-cn and https://www.npmjs.com/package/@klingai/cli-cn
The two regions use separate accounts and credits. Generation consumes account credits. Kling's API release notes document Kling 4.0 4K and HDR support; those API capabilities should not be presented as guaranteed MCP tool parameters because tool availability depends on the connected account and current tool declarations.
Disclosure: I work at Kling and am suggesting this integration as part of product promotion. This is a directory request, not an independent hands-on evaluation; I have not run a generation test for this submission.
OpenHands AI triage
The following comments and acceptance criteria were added by the OpenHands AI agent.
Triage
Scope: one hand-authored file, integrations/catalog/kling-ai.json, plus the regenerated integrations/catalog-index.js from npm run build:integrations - exactly what repository governance requires for a new integration. The entry carries two hosted OAuth MCP connection options (Global kling.ai first, China klingai.com second), matching the request for one official entry with separate regional connections.
Verified by this triage: all four npm packages (@klingai/plugin-global, @klingai/cli-global, @klingai/plugin-cn, @klingai/cli-cn) exist on the registry; the official guide (https://kling.ai/app/mcp/guide) renders and documents the 18-tool MCP surface, credit consumption, 5 QPS rate limit, and 24-hour result-URL validity; OAuth discovery metadata is live for both regions (https://kling.ai/.well-known/oauth-protected-resource and https://klingai.com/.well-known/oauth-protected-resource point to authorization servers at https://kling.ai/auth and https://klingai.com/auth, which publish authorize/token/register endpoints, S256 PKCE, and token_endpoint_auth_methods_supported: ["none"], so dynamic client registration needs no client secret); and both MCP endpoints return 401 unauthenticated. The packages' mcp.json confirms https://kling.ai/mcp/plugin and https://klingai.com/mcp/plugin as the canonical plugin URLs, with scopes generation.create, generation.read, account.credit.read matching the served metadata.
Priority: low - a vendor directory request disclosed as product promotion, with no user report, support evidence, or production impact; the default priority applies.
Non-goals: no CLI/stdio connection option (the CLI packages are thin MCP clients, not MCP servers); no connectionModel unless its identityMapping paths are verified against Kling's documented OAuth behavior; no popularityRank; no bespoke logo unless a verifiable vendor-hosted asset URL is found; no coverage of other agents' plugin or CLI installation flows; no runtime code beyond the catalog entry and its regenerated index; no presentation of API release-note capabilities (Kling 4.0 4K/HDR) as guaranteed MCP tool parameters.
Acceptance Criteria
-
integrations/catalog/kling-ai.jsonis the only hand-authored file added,integrations/catalog-index.jsis the only other file changed, and runningnpm run build:integrationsa second time produces no further diff. - The entry passes
integrations/catalog.schema.jsonand the repository test suite, includingtests/test_catalog_schema.py,tests/test_catalogs.py, andtests/test_integration_catalog_in_sync.py, with theTestsworkflow green on the PR head. - The entry
idmatches its filename anddocsUrlishttps://kling.ai/app/mcp/guide, which is reachable and describes Kling MCP setup. - The entry declares exactly two
provider: "mcp"connection options withshttptransports - Global (https://kling.ai/mcp/plugin) first and China (https://klingai.com/mcp/plugin) second - and each transport URL is one whose resource is served by that region's/.well-known/oauth-protected-resourcemetadata (e.g. resourcehttps://kling.ai/mcp/pluginfor the Global URL). - Each option's OAuth fields match the live authorization-server metadata for its region (
https://kling.ai/auth/.well-known/oauth-authorization-serverorhttps://klingai.com/auth/.well-known/oauth-authorization-server):authorizationUrl,tokenUrl, andregistrationUrlequal the servedauthorization_endpoint,token_endpoint, andregistration_endpoint; scopes aregeneration.create,generation.read,account.credit.read; PKCE uses S256; and no client secret is required (token_endpoint_auth_methods_supportedincludesnone). - The entry stores no credential material or client secret, and an unauthenticated POST to each transport URL still returns 401.
- The entry's description or notes state that the Global and China regions use separate accounts and credits and that generation consumes account credits.
- No text in the entry presents API-only capabilities (Kling 4.0 4K, HDR) as guaranteed MCP tool parameters; tool availability is described as depending on the connected account and the server's current tool declarations (
who_am_i). - No connection option launches the CLI npm packages via stdio (they are MCP clients, not MCP servers); npm package names, if referenced at all, appear only in
installHintor notes as setup context. - Adding the integration in OpenHands shows the Kling entry with the two regional connection options, and starting the Global OAuth connection reaches Kling's sign-in at
https://kling.ai/auth/authorizeand completes an authorized MCP connection for a reviewer with a Kling account (the China option analogously completes viahttps://klingai.com/auth/authorizewhere the reviewer has a China-region account).
- Lingua principale
- Python
- Stelle
- 184
- Fork
- 137
- Merge medio
- 1g 19h
- PR unite (30g)
- 46
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di OpenHands/extensions
-
priority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
OpenHands/extensions#975 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
OpenHands/extensions#970 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
OpenHands/extensions#969 ·
I maintainer di solito rispondono entro 1 giorno
-
Add a `maven` skill: agents install Debian's `maven` package, which can't load plugins built for Java 17+Forse già presa @sumitvairagar l’ha presa 3 giorni fa. Apertapriority:medium ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
OpenHands/extensions#963 ·
I maintainer di solito rispondono entro 1 giorno
-
agent-readiness-report: scan_build_env.sh misses lowercase `justfile` and `just` build commandsForse già presa @austinchennn l’ha presa 2 giorni fa. Apertapriority:low ready-for-dev
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
OpenHands/extensions#955 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di OpenHands/extensions
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
huggingface/datasets#9128 ·
I maintainer di solito rispondono entro 1 giorno
-
Function/dict state handlers can't supply provider-state injected values (`generate.provider_state`)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
pact-foundation/pact-python#1789 ·
I maintainer di solito rispondono entro 9 giorni
-
documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
juandresrodca/AdminForge#66 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
backend/local comp/tools P2 tool/terminal type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
NousResearch/hermes-agent#158788 ·
I maintainer di solito rispondono entro 1 giorno