Create MCP server directory structure #20

New Issue

cardosofelipe · 2025-12-29T23:46:00Z

cardosofelipe commented

2025-12-29 23:46:00 +00:00

Description

Set up the directory structure and base classes for MCP (Model Context Protocol) servers.

Requirements

Directory Structure

mcp/
├── __init__.py
├── base/
│   ├── __init__.py
│   ├── server.py         # Base MCP server class
│   └── types.py          # Common MCP types
├── llm_gateway/          # Phase 2
├── knowledge_base/       # Phase 2
├── git_ops/              # Phase 2
├── issues/               # Phase 2
└── README.md             # MCP development guide

Base Server Class

FastMCP-based server template
Standard tool registration pattern
Project scoping utilities
Error handling patterns

Documentation

How to create a new MCP server
Tool naming conventions
Project scoping requirements

Acceptance Criteria

Directory structure created
Base server class with project scoping
Type definitions for common patterns
README with development guide
Example tool registration

Technical Notes

Reference: ADR-004 (MCP-first architecture)
Reference: ADR-005 (LiteLLM integration via MCP)
All tools must accept project_id for scoping

Assignable To

backend-engineer agent

## Description Set up the directory structure and base classes for MCP (Model Context Protocol) servers. ## Requirements ### Directory Structure ``` mcp/ ├── __init__.py ├── base/ │ ├── __init__.py │ ├── server.py # Base MCP server class │ └── types.py # Common MCP types ├── llm_gateway/ # Phase 2 ├── knowledge_base/ # Phase 2 ├── git_ops/ # Phase 2 ├── issues/ # Phase 2 └── README.md # MCP development guide ``` ### Base Server Class - FastMCP-based server template - Standard tool registration pattern - Project scoping utilities - Error handling patterns ### Documentation - How to create a new MCP server - Tool naming conventions - Project scoping requirements ## Acceptance Criteria - [ ] Directory structure created - [ ] Base server class with project scoping - [ ] Type definitions for common patterns - [ ] README with development guide - [ ] Example tool registration ## Technical Notes - Reference: ADR-004 (MCP-first architecture) - Reference: ADR-005 (LiteLLM integration via MCP) - All tools must accept `project_id` for scoping ## Assignable To backend-engineer agent

cardosofelipe added the backend phase-0 labels 2025-12-29 23:49:40 +00:00

cardosofelipe referenced this issue from a commit

2025-12-30 01:14:05 +00:00

feat: Add MCP server stubs, development docs, and Docker updates

cardosofelipe closed this issue

2025-12-30 01:14:18 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cardosofelipe/syndarix#20