MCP-Server

What is MCP-Server?

MCP-Server is a microservice architecture that provides various services for a Management Control Panel (MCP). It consists of several independent microservices, each offering specific functionality. The project includes services such as the MCP GuruFocus Service for financial data integration and the MCP TG JIRA SeminarApp Service for JIRA and Zephyr test management integration.

How to use MCP-Server?

Clone the repository and create a .env file for each service based on the provided .env.template. Each microservice runs in its own Python 3.12 virtual environment and uses uv as the package manager. To add a new microservice, run the ./new_mcp_server.sh setup script.

Key features of MCP-Server

• Microservice architecture for modular functionality.
• Integration with GuruFocus for financial data (stocks, ratios, estimates, news).
• Integration with JIRA and Zephyr for test management (projects, requirements, test cases, test runs).
• Each service uses Python 3.12 with isolated virtual environments.
• Managed via pyproject.toml and uv package manager.

Use cases of MCP-Server

• Access financial data such as stock information and analyst estimates from GuruFocus.
• Manage JIRA projects, requirements, test cases, and test executions.
• Add new microservices to extend MCP functionality using the provided setup script.

FAQ from MCP-Server

What microservices are included?

The README describes the MCP GuruFocus Service (financial data endpoints) and the MCP TG JIRA SeminarApp Service (JIRA/Zephyr test management endpoints).

How do I set up a microservice?

Create a .env file for each service based on the .env.template. Each service requires Python 3.12 and uses uv as the package manager.

What are the dependencies for development?

Each microservice runs Python 3.12, has its own virtual environment, and uses pyproject.toml with uv for package management.

How can I add a new microservice?

Run the ./new_mcp_server.sh script to set up a new MCP server microservice.

What runtime or authentication is required?

The README does not specify runtime environments or authentication methods. Each service may define its own configuration via the .env file.