MCP server mode: client compatibility tests and setup recipes
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- rust
- Ambito
- cli, documentation, testing
Direzione di ricerca
Read docs/guide/mcp-server.md and apps/cli/src/mcp_serve/tests.rs to understand the current guide and test harness; inspect apps/cli/src/mcp_serve.rs and crates/daemon-api/src/mcp_server.rs for the server and HTTP facade. Start by running the existing CLI tests, then map the proposal into conformance tests and client recipes. Done means the requested compatibility coverage passes in Linux and Windows CI, and the guide and index include client setup and troubleshooting.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
size: M · first-timer: no
Summary
Harden bot mcp serve (Praxi as an MCP server for other agents) with an end-to-end compatibility test suite driven by a real MCP client, and publish tested setup recipes for the common MCP clients.
Why it matters
bot mcp serve lets Claude Code, Cursor, an IDE or any MCP client hand tasks to a Praxi bot and, optionally, use its browser and desktop tools. That is a strong integration, but today the only documented client is a single claude mcp add line, and the protocol surface (tool schemas, cancellation, size limits, error results) is only partly covered by tests. People will try other clients and hit differences we have not seen.
Current state
docs/guide/mcp-server.mddocuments the credential flow (bot token create --scope mcp:tasks), the task tools (bot_list,task_start,task_status,task_result,task_cancel,schedule_list), the optionalcomputerlayer, approvals, limits and revocation.apps/cli/src/mcp_serve.rs(layersLayer::TasksandLayer::Computer, stdio transport only) andapps/cli/src/mcp_serve/tests.rs.rmcpis already a dependency, with itsclientfeature in the dev dependencies ofapps/cli.- The HTTP facade it talks to is
GET /v1/mcp-server/toolsandPOST /v1/mcp-server/callincrates/daemon-api/src/mcp_server.rs. - There is no inbound MCP HTTP listener, by design.
Proposal and suggested approach
- Conformance tests. A test that starts the real
bot mcp serveprocess against the in-process daemon with the fake provider and drives it with thermcpclient:initialize, capability negotiation,tools/list(assert every schema is valid JSON Schema and descriptions are present), the full task life cycle, cancellation mid-run, a credential that is expired or revoked, over-limit inputs, a rate-limited call, and malformed frames. Keep it hermetic (no network, no keys). - Tool metadata. Review the exported tools for sensible annotations (read-only vs. changes state) and stable, documented names; list them in the docs table.
- Client recipes. A "Connect your MCP client" section with configuration for at least Claude Code, Claude Desktop, Cursor and VS Code, plus a generic stdio example. Mark each recipe as verified (with the client version you used) or unverified; do not guess.
- Troubleshooting. The three or four failures people will hit (keychain not reachable from the client's launch environment, wrong data dir, expired token, client timeouts during approval) with the exact message and fix.
Acceptance criteria
- The new tests run in
cargo test -p clion Linux and Windows CI without extra setup and fail loudly if a tool schema or the life-cycle semantics change. - Docs: recipe section and troubleshooting added to
docs/guide/mcp-server.mdand linked fromdocs/guide/index.md. - No change to the authority model described in the guide (approvals, scopes, limits).
Out of scope
An HTTP/SSE transport for the server, new tool layers, changing approval semantics, anything that lets an MCP client approve an action.
How to get started
Read docs/guide/mcp-server.md, then apps/cli/src/mcp_serve/tests.rs for the existing harness. Comment here to claim it; PRs that only add one verified client recipe are also welcome.
- Lingua principale
- Rust
- Stelle
- 0
- Fork
- 1
- Merge medio
- 6h 54m
- PR unite (30g)
- 152
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la 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 emreocell/Praxi-Bot
-
area: desktop-ui enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
Add an LLM provider presetApertaarea: daemon enhancement good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno
-
Contribute example skillsApertadocumentation enhancement good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue help wanted
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
emreocell/Praxi-Bot#168 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di emreocell/Praxi-Bot
Issue simili
-
bug ui
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
userFRM/egui-charts#3363 ·
I maintainer di solito rispondono entro 1 giorno
-
ada documentation mobile report
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
physicsdolphin/nv-uefi-unlocker#254 · 2 reazioni ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
kindraywind/rustnarok-client#1382 ·
I maintainer di solito rispondono entro 1 giorno
-
area:accessibility bug good first issue help wanted priority:p3-low size:small
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
NecturaLabs/Canopy#209 ·
-
CLI config custom-model enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno