You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maka.apache.org by "Phoenix500526 (via GitHub)" <gi...@apache.org> on 2026/08/31 07:50:24 UTC

[I] tracking(mcp): complete the post-V3 roadmap [maka]

Phoenix500526 opened a new issue, #4329:
URL: https://github.com/apache/maka/issues/4329

   ## Problem
   
   The dual-era MCP V3 rollout is complete in #1650, but the architecture document
   still lists post-V3 work without one current coordination tracker. Some slices
   have since shipped or gained their own tracker, while the remaining ownership
   is fragmented.
   
   ## Desired outcome
   
   Maintain one authoritative view of MCP work after V3. Each implementation slice
   may use its own focused issue and PR; this tracker closes when every item is
   either shipped or linked to a durable child tracker and the architecture
   document reflects its current state.
   
   ## Checklist
   
   - [x] Ship OAuth discovery, PKCE, dynamic client registration, Desktop login, and secret-safe IPC (#2919, #2920)
   - [ ] Move MCP tokens and remaining credential-bearing configuration to platform-backed secret storage
   - [ ] Add resources/templates browse, read, subscribe/unsubscribe, and host UI
   - [ ] Add an authenticated loopback MCP proxy for controlled subprocess clients
   - [ ] Give config reload, per-server health, bounded backoff, and crash recovery one lifecycle owner; coordinate with #3838
   - [ ] Define finer-grained MCP permission policy without trusting server annotations
   - [ ] Add signed remote catalogs, last-known-good caching, guided setup schema, package provenance, and update permission diffs
   - [ ] Keep the architecture document synchronized as child work lands
   
   ## Non-goals
   
   - Reopening the completed protocol rollout in #1650
   - Duplicating TUI MCP management or remote publication from #3838/#4200
   - Delivering the roadmap as one large PR
   - Moving Client-owned MCP transports or child-process ownership into Runtime Host
   - Adding MCP Apps, Tasks, or `input_required` handling here
   
   ## Documentation
   
   - [MCP runtime architecture](https://github.com/apache/maka/blob/main/docs/architecture/mcp-runtime-architecture-draft.zh-CN.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] tracking(mcp): complete the post-V3 roadmap [maka]

Posted by "github-actions[bot] (via GitHub) via commits" <co...@maka.apache.org>.
github-actions[bot] closed issue #4329: tracking(mcp): complete the post-V3 roadmap
URL: https://github.com/apache/maka/issues/4329


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] tracking(mcp): complete the post-V3 roadmap [maka]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #4329:
URL: https://github.com/apache/maka/issues/4329#issuecomment-5924408258

   <!-- maka-lifecycle:stale-warning -->
   This issue has had no human activity for 30 days and has been marked stale. It will be closed in 30 days unless someone comments.
   
   If the issue is still current, please confirm it against the latest `main` and add any information that would help move it forward. Assigned issues and issues labelled `pinned` are exempt from this policy.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org


Re: [I] tracking(mcp): complete the post-V3 roadmap [maka]

Posted by "github-actions[bot] (via GitHub) via commits" <co...@maka.apache.org>.
github-actions[bot] commented on issue #4329:
URL: https://github.com/apache/maka/issues/4329#issuecomment-6552996663

   <!-- maka-lifecycle:stale-close -->
   This issue has been closed because it received no human response during the 30-day grace period. This is not a judgement on the value of the report.
   
   If the issue still applies to the latest `main`, please comment with updated evidence so a maintainer can reopen it, or open a follow-up issue with the missing information.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@maka.apache.org
For additional commands, e-mail: commits-help@maka.apache.org