Azure / Azure/documentdb-agent-kit

Unblock plugin installs in Claude / Codex / Gemini / Copilot / Cursor / VS Code

Aperta
#20 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
Lingua principale
Shell
Stelle
5
Fork
10
Merge medio
2g 15h
PR unite (30g)
1

Descrizione

# Unblock plugin installs in Claude / Codex / Gemini / Copilot / Cursor / VS Code

## Problem

The plugin scaffolding in this repo (`.claude-plugin/`, `.codex-plugin/`, `.cursor-plugin/`, `gemini-extension.json`, `mcp.json`) all reference an npm package that doesn't exist:

```json
"command": "npx",
"args": ["-y", "documentdb-mcp-server"]
```

```
$ npm view documentdb-mcp-server
npm error 404 Unpublished on 2025-04-17T14:13:45.796Z
```

So **the plugin installs are broken in every client today**. v2 will publish to npm under a scoped name; this issue tracks the **interim fix** so customers can use the plugins now.

## Approach

Switch every plugin config from the dead npm name to the public-GitHub spec that `npx` understands natively:

```json
"args": ["-y", "github:microsoft/documentdb-mcp#v1.0.0"]
```

This requires `microsoft/documentdb-mcp` to be public first — tracked in [microsoft/documentdb-mcp#TBD](https://github.com/microsoft/documentdb-mcp/issues).

## Tasks (in order)

- [ ] Wait for `microsoft/documentdb-mcp` to be made public and tagged `v1.0.0`
- [ ] Open PR swapping the MCP command in **all** of these files in lockstep:
- [ ] `mcp.json`
- [ ] `.claude-plugin/plugin.json` (if it duplicates the command — currently inherits from `mcp.json`)
- [ ] `.codex-plugin/` configs
- [ ] `.cursor-plugin/` configs
- [ ] `gemini-extension.json`
- [ ] `README.md` install snippets
- [ ] `AGENTS.md` / `GEMINI.md` / `CLAUDE.md` if any hardcode a command
- [ ] Tag agent-kit `v1.0.0` after merge so marketplaces have a stable ref
- [ ] Pin a discussion explaining v1 ships from GitHub and v2 will move to npm (no breaking change for customers)

## Validation matrix — gate before announcing

Install the plugin end-to-end in each client at least once and confirm `list_databases` works:

| Client | Pass? | Notes |
|---|---|---|
| Claude Code (`/plugin install`) | ☐ | Most likely to choke on cold-start TS compile under `npx` |
| Claude Desktop (`claude_desktop_config.json`) | ☐ | |
| Codex CLI | ☐ | |
| Cursor (deep-link install badge) | ☐ | |
| GitHub Copilot CLI | ☐ | |
| VS Code (deep-link install badge) | ☐ | |
| Gemini CLI | ☐ | |

If cold-start under `npx` is too slow (> 60 s) in any client, escalate v2 npm publish — see [microsoft/documentdb-mcp#TBD](https://github.com/microsoft/documentdb-mcp/issues).

## Pinning: tag vs branch

Pin to `#v1.0.0` (the tag), not `#main`. Tag pinning prevents customers from breaking when `main` moves; hotfixes can ship as `v1.0.1` etc.

## Out of scope

- npm publish (tracked separately as v2)
- Org transfer to `Azure/` (tracked separately)

## Done when

- All four+ plugin configs reference the tagged public GitHub spec
- All six clients in the validation matrix install + work
- Pinned discussion is up
- agent-kit `v1.0.0` tag exists

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Verifica innanzitutto che microsoft/documentdb-mcp sia pubblico e abbia il tag v1.0.0, quindi esamina mcp.json, le configurazioni di .claude-plugin/, .codex-plugin/ e .cursor-plugin/, gemini-extension.json, README.md e tutte le istruzioni degli agenti elencate per individuare comandi hardcoded. Convalida l'installazione e list_databases sui client della matrice, quindi conferma che la discussione e il tag v1.0.0 di agent-kit siano presenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
github, node.js
Ambito
release, tooling
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
45/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.