Merge pull request #20 from shrug-labs/rigebha/publish

Welcome to OCI to the repo :
add OCI MCP servers

Author: krisrice

.github/workflows/build.yml

@@ -0,0 +1,74 @@
+name: Matrix Build
+on:
+  push:
+    branches:
+      - "main"
+  pull_request:
+    branches:
+      - "main"
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    needs: get-directories
+    strategy:
+      matrix:
+        directory: ${{ fromJson(needs.get-directories.outputs.directories) }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.13'
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v6
+        with:
+          version: "0.8.19"
+
+      - name: Install tomlq
+        run: pip install tomlq
+
+      - name: Update __init__.py
+        working-directory: src/${{ matrix.directory }}
+        run: |
+          name=$(uv run tomlq -r '.project.name' pyproject.toml)
+          version=$(uv run tomlq -r '.project.version' pyproject.toml)
+          if [ -d oracle/*_mcp_server ]; then
+            init_py_file=oracle/*_mcp_server/__init__.py
+            echo "\"\"\"\nCopyright (c) 2025, Oracle and/or its affiliates.\nLicensed under the Universal Permissive License v1.0 as shown at\nhttps://oss.oracle.com/licenses/upl.\n\"\"\"\n" > $$init_py_file; \
+            echo "__project__ = \"$name\"" >> $init_py_file
+            echo "__version__ = \"$version\"" >> $init_py_file
+          fi
+
+      - name: Sync
+        working-directory: src/${{ matrix.directory }}
+        run: uv sync --locked --all-extras --dev
+
+      - name: Test
+        working-directory: src/${{ matrix.directory }}
+        run: uv run pytest
+
+      - name: Build
+        working-directory: src/${{ matrix.directory }}
+        run: uv build
+
+      - name: Test install
+        working-directory: src/${{ matrix.directory }}
+        run: uv pip install .
+
+
+  get-directories:
+    runs-on: ubuntu-latest
+    outputs:
+      directories: ${{ steps.get-directories.outputs.directories }}
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Get directories
+        id: get-directories
+        run: |
+          directories=$(ls src | grep -v dbtools-mcp-server | grep -v mysql-mcp-server | grep -v oci-pricing-mcp-server | jq -R -s -c 'split("\n")[:-1]')
+          echo "directories=$directories" >> $GITHUB_OUTPUT

.github/workflows/lint.yml

@@ -0,0 +1,24 @@
+name: Lint
+on:
+  push:
+    branches: 
+      - "main"
+  pull_request:
+    branches:
+      - "main"
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v4
+    - name: Set up Python ${{ matrix.python-version }}
+      uses: actions/setup-python@v3
+      with:
+        python-version: ${{ matrix.python-version }}
+    - name: Install dependencies
+      run: |
+        python -m pip install --upgrade pip
+        python -m pip install -r requirements-dev.txt
+    - name: Test with tox
+      run: |
+        tox run -e lint

.gitignore

@@ -1,4 +1,4 @@
-__pycache__/
+**/__pycache__/**
 
 # Virtual environment
 venv/
@@ -9,3 +9,6 @@ env/
 env.bak/
 venv.bak/
 
+
+# test environments
+.env

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to make participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <[email protected]>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -1,3 +1,5 @@
+*Detailed instructions on how to contribute to the project, if applicable. Must include section about Oracle Contributor Agreement with link and instructions*
+
 # Contributing to this repository
 
 We welcome your contributions! There are multiple ways to contribute.
@@ -35,14 +37,14 @@ can be accepted.
 
 1. Ensure there is an issue created to track and discuss the fix or enhancement
    you intend to submit.
-1. Fork this repository
-1. Create a branch in your fork to implement the changes. We recommend using
-   the issue number as part of your branch name, e.g. `1234-fixes`
-1. Ensure that any documentation is updated with the changes that are required
+2. Fork this repository.
+3. Create a branch in your fork to implement the changes. We recommend using
+   the issue number as part of your branch name, e.g. `1234-fixes`.
+4. Ensure that any documentation is updated with the changes that are required
    by your change.
-1. Ensure that any samples are updated if the base image has been changed.
-1. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
-   what your changes are meant to do and provide simple steps on how to validate
+5. Ensure that any samples are updated if the base image has been changed.
+6. Submit the pull request. *Do not leave the pull request blank*. Explain exactly
+   what your changes are meant to do and provide simple steps on how to validate.
    your changes. Ensure that you reference the issue you created as well.
 1. We will assign the pull request to 2-3 people for review before it is merged.
 
@@ -52,4 +54,4 @@ Follow the [Golden Rule](https://en.wikipedia.org/wiki/Golden_Rule). If you'd
 like more specific guidelines, see the [Contributor Covenant Code of Conduct][COC].
 
 [OCA]: https://oca.opensource.oracle.com
-[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/
+[COC]: https://www.contributor-covenant.org/version/1/4/code-of-conduct/

Makefile

@@ -0,0 +1,58 @@
+SUBDIRS := $(wildcard src/*)
+
+.PHONY: test format
+
+build:
+	@for dir in $(SUBDIRS); do \
+		if [ -f $$dir/pyproject.toml ]; then \
+			echo "Building $$dir"; \
+			name=$$(uv run tomlq -r '.project.name' $$dir/pyproject.toml); \
+			version=$$(uv run tomlq -r '.project.version' $$dir/pyproject.toml); \
+			if [ -d $$dir/oracle/*_mcp_server ]; then \
+				init_py_file=$$(echo $$dir/oracle/*_mcp_server/__init__.py); \
+				echo "\"\"\"\nCopyright (c) 2025, Oracle and/or its affiliates.\nLicensed under the Universal Permissive License v1.0 as shown at\nhttps://oss.oracle.com/licenses/upl.\n\"\"\"\n" > $$init_py_file; \
+				echo "__project__ = \"$$name\"" >> $$init_py_file; \
+				echo "__version__ = \"$$version\"" >> $$init_py_file; \
+			fi; \
+			cd $$dir && uv build && cd ../..; \
+		fi \
+	done
+
+install:
+	@for dir in $(SUBDIRS); do \
+		if [ -f $$dir/pyproject.toml ]; then \
+			echo "Installing $$dir"; \
+			cd $$dir && uv pip install . && cd ../..; \
+		fi \
+	done
+
+sync:
+	@for dir in $(SUBDIRS); do \
+		if [ -f $$dir/pyproject.toml ]; then \
+			echo "Installing $$dir"; \
+			cd $$dir && uv sync --locked --all-extras --dev && cd ../..; \
+		fi \
+	done
+
+lock:
+	@for dir in $(SUBDIRS); do \
+		if [ -f $$dir/pyproject.toml ]; then \
+			echo "Installing $$dir"; \
+			cd $$dir && uv lock && cd ../..; \
+		fi \
+	done
+
+test:
+	uv tool run --from 'tox==4.30.2' tox -e lint
+	@for dir in $(SUBDIRS); do \
+		if [ -f $$dir/pyproject.toml ]; then \
+			echo "Testing $$dir"; \
+			cd $$dir && uv run pytest && cd ../..; \
+		fi \
+	done
+
+format:
+	uv tool run --from 'tox==4.30.2' tox -e format
+
+e2e-tests: build install
+	behave tests/e2e/features && cd ..