diff --git a/meetings/2026-07-08_weekly.md b/meetings/2026-07-08_weekly.md
new file mode 100644
index 0000000..58f3242
--- /dev/null
+++ b/meetings/2026-07-08_weekly.md
@@ -0,0 +1,67 @@
+# 2026-07-08 MCP: Transport Working Group (Weekly)
+
+## TL;DR
+The Transport Working Group aligned on major architectural updates regarding
+tool capabilities, agreeing to focus exclusively on client-side tool annotations
+to simplify protocol complexity. The team also finalized a roadmap for streaming
+and internationalization, discussed SDK pagination and caching mechanisms, and
+explored rescheduling the weekly meeting to better accommodate international
+members.
+
+## Detailed Summary
+
+### Technical Protocol Updates & Caching
+* The team discussed caching mechanisms for tool lists using unique version
+  keys.
+* Shaun Smith and the group will work on drafting explicit guidance regarding
+  what constitutes a cache key for implementations to follow to ensure
+  consistent client-server coordination.
+* In the Software Development Kit (SDK), pagination issues were identified and
+  clarified as distinct from current caching pull requests.
+
+### Refining Tool Capability Models
+* The group discussed a decision regarding capability model design, discussing a
+  focus on client-side tool annotations vs server-side filtering.
+* Client-side annotation simplifies the overall protocol implementation and
+  avoids unnecessary caching complexity for proxies.
+* Gabriel Zimmerman will develop the next version of the tool capabilities
+  proposal and outline use cases/examples where elicitation capabilities impact
+  tool calls.
+
+### Roadmap Planning & Meeting Schedule
+* The working group discussed the roadmap covering upcoming goals like streaming
+  capabilities and internationalization.
+* The July specification release remains on track, with preview versions already
+  available for testing.
+* To improve collaboration across differing time zones, the group debated
+  potential rescheduling, including a possible move to Friday mornings.
+
+## Next Steps & Timeline
+Between now and the next meeting, Kurtis Van Gent will propose a new meeting
+time on Discord to collect team feedback and finalize the schedule.
+Additionally, Kurtis will draft the roadmap document and prepare the sessions
+documentation. Shaun Smith will finish work on streaming and caching
+specifications and clean up the caching change pull request. Gabriel Zimmerman
+will refine the tool capabilities proposal and document elicitation examples.
+
+## Action Items
+- [ ] **Shaun Smith** Review PR: Review the caching change pull request and
+  remove unnecessary elements.
+- [ ] **Shaun Smith** Finish Streaming Specs: Complete the streaming work for
+  the project.
+- [ ] **Shaun Smith** Complete Caching Specs: Finalize the caching requirements
+  and documentation.
+- [ ] **Kurtis Van Gent** Propose Meeting Time: Propose a new meeting time in
+  the Discord channel for team feedback and finalize the schedule to better
+  accommodate members in different time zones.
+- [ ] **Kurtis Van Gent** Draft Roadmap: Create a roadmap document outlining the
+  goals and tasks for the upcoming months, with one paragraph per identified
+  problem.
+- [ ] **Kurtis Van Gent** Write Sessions Document: Prepare the sessions
+  documentation as discussed in the meeting.
+- [ ] **Gabriel Zimmerman** Define Capabilities: Develop the next version of the
+  tool capabilities proposal.
+- [ ] **Gabriel Zimmerman** Document Elicitation Examples: Write down use cases
+  and examples where elicitation capabilities impact tool calls.
+- [ ] **The group** Document Caching Guidance: Draft explicit guidance on what
+  constitutes a cache key for implementations to follow.