[Fixes #146] chore: restructure repository for agentic RAG and rename docs-agent-mcp to kagent-feast-mcp

[alwaysalearner1234]

Description

As the project evolves towards a more modern, agentic RAG architecture (as outlined in gsoc2026_agentic_rag.md), the current repository structure contains several monolithic server implementations that are no longer the primary focus.

This PR tracks the necessary repository restructuring to reflect our new architectural direction and standardizes the nomenclature around the new agent configuration.

Changes Included

• Deprecated Legacy Servers: Moved the existing server/ and server-https/ implementations (previously under legacy/) into a new legacy-servers/ directory at the repository root. This signals their outdated status while safely maintaining backward compatibility.
• Prioritized Kagent: Updated the primary deployment directory from docs-agent-mcp/ to kagent-feast-mcp/ to align with the new architectural blueprint.
• Documentation Updates: Updated the root README.md to explicitly highlight the kagent-feast-mcp/ setup as the recommended, primary deployment path.
• Widespread Path Updates: Updated all paths referencing the old docs-agent-mcp directory across:
  • CI/CD (oke-cicd.yaml, tests.yml)
  • Testing suite (tests/)
  • Configurations (pyproject.toml, .gitignore)

Motivation and Context

This restructuring strongly aligns with the recent community direction toward kagent and the Model Context Protocol (MCP). Implementing these changes provides several benefits:

• Cleaner Workspace: Ensures a much cleaner and more navigable root directory.
• Improved Onboarding: Provides a streamlined onboarding experience for new users and contributors by pointing them directly to the current architectural targets.
• Reduced Confusion: Eliminates ambiguity between the older monolithic server approaches and the new agentic RAG setup.

References

• Ref: Community feedback regarding the kagent transition (PR feat: implement ContextWindowManager and Global Encoder Singleton for… #145)
• Note: This architectural update is proposed as part of my Google Summer of Code (GSoC) 2026 project.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring / Chore (changing repository structure, paths, etc.)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• Existing tests are updated to point to the new paths

#146

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tarekabouzeid for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[SanthoshToorpu]

Was this bought up before this @alwaysalearner1234?

[alwaysalearner1234]

No, I don't think this was brought up before. I came across this as part of the changes proposed in PR #146, especially the restructuring around "legacy-servers/" and prioritizing "kagent-feast-mcp/".