Add Data Olympus

[ajdelaguila]

Description

Adds Data Olympus to the MCP Servers section. Data Olympus is a local governed project-knowledge MCP server for AI coding agents, with reviewed learning proposals and in-force retrieval.

Type of contribution

• Plugin/Extension
• MCP Server
• Editor Plugin/Integration
• Documentation/Resource
• Other (please specify)

Submission checklist

• I have read the contribution guidelines (if any)
• The item is awesome and relevant to Claude Code
• The link is working and leads to the correct resource
• The description is clear and concise
• The item is added in the appropriate category
• The item follows the existing format
• I have verified that this item is not already in the list

Additional context

Data Olympus v0.4.0 added validity windows, supersession-aware retrieval, and in-force filtering so stale or unreviewed project guidance does not silently enter future Claude Code sessions.

[qodo-code-review]

PR Summary by Qodo

Add Data Olympus MCP server to README list

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Add Data Olympus to the MCP servers table.
• Update MCP server count to reflect the new entry.
• Fix README newline at end-of-file for clean formatting.

High-Level Assessment

The PR follows the repository’s existing pattern (table entry + summary metric). No alternative approach is meaningfully better for adding a new MCP server to the list.

Files changed (1) +3 / -2

Documentation (1) +3 / -2

README.mdList Data Olympus MCP server and update server count +3/-2

List Data Olympus MCP server and update server count

• Adds a new row for Data Olympus in the MCP servers table with its link, auth type, and coverage description. Updates the top-level MCP server count from 5 to 6 and normalizes the file to include a trailing newline.

README.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Stale update metadata 🐞 Bug ⚙ Maintainability

Description

README.md updates the MCP server count and adds a new MCP server entry, but leaves the Status
table's "Last updated" value as "2025-Q2". This creates documentation drift where the freshness
indicator no longer matches the content changes in this PR.

Code

README.md[R9-13]

| Plugins listed | 4 |
-| MCP servers | 5 |
+| MCP servers | 6 |
| Editor integrations | 6 |
| Learning resources | 5 |
| Last updated | 2025-Q2 |

Evidence

The Status table shows MCP servers updated to 6 while still reporting Last updated | 2025-Q2, and
the MCP Servers section includes the newly added Data Olympus entry, indicating the list has been
modified after that timestamp.

README.md[7-13]
README.md[34-44]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The README Status table's `Last updated` field was not updated even though the list contents and counts changed in this PR.

### Issue Context
The Status table now says MCP servers = 6, and the MCP server list includes a newly added entry, but `Last updated` remains `2025-Q2`.

### Fix Focus Areas
- README.md[7-13]

### Suggested fix
Update `Last updated` to the appropriate current quarter/date for this change (or remove the field if it is not intended to be maintained).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

1. Stale update metadata 🐞 Bug ⚙ Maintainability

README.md updates the MCP server count and adds a new MCP server entry, but leaves the Status
table's "Last updated" value as "2025-Q2". This creates documentation drift where the freshness
indicator no longer matches the content changes in this PR.

Agent Prompt

### Issue description
The README Status table's `Last updated` field was not updated even though the list contents and counts changed in this PR.

### Issue Context
The Status table now says MCP servers = 6, and the MCP server list includes a newly added entry, but `Last updated` remains `2025-Q2`.

### Fix Focus Areas
- README.md[7-13]

### Suggested fix
Update `Last updated` to the appropriate current quarter/date for this change (or remove the field if it is not intended to be maintained).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools