MCP Registry onboarding request: Weft (com.letsweft/weft) — remote OAuth server

[AndreiFinogeev]

Following up on #1257, where the answer was that onboarding a server to the GitHub MCP Registry is still a manual curation step even after it is published to the OSS registry. Requesting onboarding for Weft.

What it is. A shared Scrumban board for a person and the AI agents working for them. Agents claim tasks with a lease, report progress, and finish with a receipt — what they changed, what they did not do, what they were unsure about — which the person accepts or returns from an inbox. The point is that work done in one client is visible in all the others, and to the human, on the web or a phone.

The listing

Registry entry	com.letsweft/weft, v0.1.1, status active
Remote endpoint	https://letsweft.com/api/mcp (streamable HTTP)
Auth	OAuth 2.1, Authorization Code + PKCE, dynamic client registration (RFC 7591) — no API keys, nothing to paste
Manifest	https://letsweft.com/.well-known/mcp.json (schemaVersion 2025-11-25)
Tools	32 — board state, tasks, columns, sprints, projects, decisions, history, and an ask-the-human channel
Repository	https://github.com/AndreiFinogeev/weft-mcp
Setup guide for VS Code	https://letsweft.com/vscode

Why we think it fits the gallery. Copilot's agent mode is exactly the case the board was built for: an agent that plans, edits and then leaves follow-ups behind. Adding the server takes one line of mcp.json and a browser sign-in; there is nothing to self-host and no key to manage.

Happy to supply anything the curation needs — a logo, a longer description, or a reviewer account.