soktri3 · soktri3 · May 6, 2026 · gemini-code-assist · May 6, 2026
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
@@ -18,7 +18,7 @@
 
 ## Checklist
 <!-- Go over all the following points, and put an `x` in all the boxes that apply. -->
-- [ ] I have read the [MCP Documentation](https://modelcontextprotocol.io)
+- [ ] I have read the [MCP Documentation](https://modelcontextprotocol.io/docs/getting-started/intro)
 - [ ] My code follows the repository's style guidelines
 - [ ] New and existing tests pass locally
 - [ ] I have added appropriate error handling

diff --git a/.jules/bolt.md b/.jules/bolt.md
@@ -1,11 +1,9 @@
-## 2025-04-22 - Logo Asset Optimization
+# Bolt Performance Journal
 
-**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
+## 2025-05-06 - Reducing HTTP Redirects in Documentation
+**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
+**Action:** Always audit documentation links for redirects and update to canonical destinations.
 
-**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
-
-## 2025-04-23 - SVG Asset Minification
-
-**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
-
-**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
+## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
+**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
+**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
-# Bolt Performance Journal
-
-**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
-## 2025-05-06 - Reducing HTTP Redirects in Documentation
-**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
-**Action:** Always audit documentation links for redirects and update to canonical destinations.
-
-**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
-
-## 2025-04-23 - SVG Asset Minification
-
-**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
-
-**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
-## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
-**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
-**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
+# Bolt Performance Journal
+
+## 2025-04-22 - Logo Asset Optimization
+**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
+**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
+
+## 2025-04-23 - SVG Asset Minification
+**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
+**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
+
+## 2025-05-06 - Reducing HTTP Redirects in Documentation
+**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
+**Action:** Always audit documentation links for redirects and update to canonical destinations.
+
+## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
+**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
+**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
-# Bolt Performance Journal
-
-**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
-## 2025-05-06 - Reducing HTTP Redirects in Documentation
-**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
-**Action:** Always audit documentation links for redirects and update to canonical destinations.
-
-**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
-
-## 2025-04-23 - SVG Asset Minification
-
-**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
-
-**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
-## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
-**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
-**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
+# Bolt Performance Journal
+
+## 2025-04-22 - Logo Asset Optimization
+**Learning:** Replacing large, static PNG assets with theme-aware SVGs significantly reduces repository weight and improves initial page load for organization profiles. SVGs (approx. 3KB) are >90% smaller than high-resolution PNGs (46KB) and maintain clarity at all sizes.
+**Action:** Always prefer SVGs for logos and simple graphics. Use the `<picture>` tag with `prefers-color-scheme` media queries to support dark and light modes on GitHub READMEs. Always specify `width` and `height` on images to prevent Cumulative Layout Shift (CLS).
+
+## 2025-04-23 - SVG Asset Minification
+**Learning:** SVG assets generated by design tools often contain significant overhead (metadata, comments, unnecessary path precision). Minifying these assets with tools like `svgo` can reduce file size by ~50% without visual degradation.
+**Action:** Always run SVGs through a minifier like `svgo` before committing. This ensures minimal asset weight and faster organization profile loading.
+
+## 2025-05-06 - Reducing HTTP Redirects in Documentation
+**Learning:** Canonicalizing URLs in documentation (e.g., from `modelcontextprotocol.io` to `modelcontextprotocol.io/docs/getting-started/intro`) eliminates unnecessary network round trips (301/302/308 redirects), providing a faster experience for users.
+**Action:** Always audit documentation links for redirects and update to canonical destinations.
+
+## 2025-05-06 - SVG Asset Optimization for GitHub Profiles
+**Learning:** Minifying SVG logos in the `profile/assets/` directory using SVGO can reduce asset size. While the savings per file might be small in this specific repo (~2-5%), it is a best practice to ensure fast profile loading and reduced bandwidth.
+**Action:** Run `npx svgo` on all new SVG assets with `--multipass --precision 1`.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -6,7 +6,7 @@ Thank you for your interest in contributing to the Model Context Protocol (MCP)!
 
 ### Issues and Discussions
 - For bugs and actionable items, please prefer creating an issue in the relevant repository
-- For open-ended or design discussions _specifically related to the specification_, use our [specification discussions](https://github.com/modelcontextprotocol/specification/discussions)
+- For open-ended or design discussions _specifically related to the specification_, use our [specification discussions](https://github.com/modelcontextprotocol/modelcontextprotocol/discussions)
 - For other general discussions that are not suitable as issues, use our [organization discussions](https://github.com/orgs/modelcontextprotocol/discussions)
 
 In all cases, please check for duplicates before creating new issues or discussions!

diff --git a/profile/CONTRIBUTING.md b/profile/CONTRIBUTING.md
@@ -4,7 +4,7 @@ Thank you for your interest in contributing to the MCP!
 
 Please find the contribution guide for the repositories in the project in the respective repository:
 
-- [Specification Contributions](https://github.com/modelcontextprotocol/specification/blob/main/CONTRIBUTING.md)
+- [Specification Contributions](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/CONTRIBUTING.md)
 - [TypeScript SDK Contributions](https://github.com/modelcontextprotocol/typescript-sdk/blob/main/CONTRIBUTING.md)
 - [Python SDK Contributions](https://github.com/modelcontextprotocol/python-sdk/blob/main/CONTRIBUTING.md)
 - [Documentation Contributions](https://github.com/modelcontextprotocol/docs/blob/main/CONTRIBUTING.md)

diff --git a/profile/README.md b/profile/README.md
@@ -13,17 +13,17 @@
 </p>
 
 <p align="center">
-  <a href="https://modelcontextprotocol.io">Documentation</a> |
-  <a href="https://spec.modelcontextprotocol.io">Specification</a> |
+  <a href="https://modelcontextprotocol.io/docs/getting-started/intro">Documentation</a> |
+  <a href="https://spec.modelcontextprotocol.io/">Specification</a> |
   <a href="https://github.com/orgs/modelcontextprotocol/discussions">Discussions</a>
 </p>
 
 The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.
 
 ## Getting Started
 
-- 📚 Read the [Documentation](https://modelcontextprotocol.io) for guides and tutorials
-- 🔍 Review the [Specification](https://spec.modelcontextprotocol.io) for protocol details
+- 📚 Read the [Documentation](https://modelcontextprotocol.io/docs/getting-started/intro) for guides and tutorials
+- 🔍 Review the [Specification](https://spec.modelcontextprotocol.io/) for protocol details
 - 💻 Use our SDKs to start building:
   - [TypeScript SDK](https://github.com/modelcontextprotocol/typescript-sdk)
   - [Python SDK](https://github.com/modelcontextprotocol/python-sdk)
@@ -33,7 +33,7 @@ The Model Context Protocol (MCP) is an open protocol that enables seamless integ
 
 ## Project Structure
 
-- [specification](https://github.com/modelcontextprotocol/specification) - Protocol specification and documentation
+- [specification](https://github.com/modelcontextprotocol/modelcontextprotocol) - Protocol specification and documentation
 - [typescript-sdk](https://github.com/modelcontextprotocol/typescript-sdk) - TypeScript implementation
 - [python-sdk](https://github.com/modelcontextprotocol/python-sdk) - Python implementation
 - [java-sdk](https://github.com/modelcontextprotocol/java-sdk) - Java implementation
@@ -51,4 +51,4 @@ Have questions? Join the discussion in our [community forum](https://github.com/
 
 ## About
 
-The Model Context Protocol is an open source project run by [Anthropic, PBC.](https://anthropic.com) and open to contributions from the entire community.
+The Model Context Protocol is an open source project run by [Anthropic, PBC.](https://www.anthropic.com/) and open to contributions from the entire community.
diff --git a/profile/assets/logo-dark.svg b/profile/assets/logo-dark.svg