Files

T

build-image / build (push) Failing after 18s

Details

Fork intervals-mcp-server: native OAuth + streamable-HTTP, no monkeypatch

- Bump mcp[cli] 1.22 -> 1.28.1 (negotiates MCP protocol 2025-11-25, matching
  current Claude clients; the old 2025-06-18 server never got a tools/list on
  the connector surface).
- Bake transport config into code: stateless_http + json_response for HTTP
  (single JSON body instead of a 34KB SSE stream, which the connector pipeline
  handles far more reliably).
- Bake Authentik OAuth (AuthSettings + JWT TokenVerifier) into intervals_mcp_server.auth,
  configured from MCP_ISSUER/MCP_RESOURCE/MCP_JWKS_URI/MCP_CLIENT_ID — removes the
  runtime FastMCP.__init__ monkeypatch from the k8s deployment command.
- Accept token audience with/without trailing slash (RFC 8707 clients use the
  slash-normalised resource metadata value).
- Dockerfile CMD runs the module (transport via MCP_TRANSPORT); add .gitea CI to
  build+push the image to git.farh.net/farhoodlabs/intervalsicu-mcp.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-04 15:07:46 -04:00

2.2 KiB

Raw Permalink Blame History

Contributing to Intervals.icu MCP Server

Thank you for taking the time to contribute! This project uses Python 3.12 and manages its dependencies with uv. The following guide summarizes how to set up your environment and outlines the workflow we expect for pull requests.

Development environment

Create a virtual environment and activate it:

uv venv --python 3.12
source .venv/bin/activate

Install all dependencies (including development extras):
```
uv sync --all-extras
```
When working on or manually running the server, use:
```
mcp run src/intervals_mcp_server/server.py
```

Dependency changes

Edit pyproject.toml.
Run uv lock (or uv sync).
Commit both pyproject.toml and uv.lock in the same commit.

If you add, remove, or relax a dependency but forget to update the lock file, CI will fail. Treat uv.lock as a first-class artifact: review it when it changes, but don’t fear committing it.

Code-only changes

For changes that do not modify dependencies, keep the lock file untouched. Run your tests with:

uv run --locked pytest

CI will also run uv lock --check to ensure uv.lock stays in sync.

Why keep the lock file?

Reproducibility – All collaborators and CI runners install identical hashes.
Security – Hash pinning in uv.lock helps prevent supply-chain attacks.
Speed – uv skips resolution when the lock matches, keeping installs lightning-fast.

Automated dependency upgrades are encouraged. You can use Dependabot, Renovate, or a scheduled GitHub Action that runs uv lock --upgrade && git push to keep the file fresh and generate tidy PRs.

Testing

Before opening a pull request, ensure all checks pass locally:

ruff check .
mypy src tests
uv run --locked pytest

Pull request guidelines

Use concise commit messages.
Title your pull request using the format [intervals-mcp-server] <brief description>.
Describe any manual testing you performed and confirm whether ruff, mypy, and pytest passed.

We appreciate your contributions and your attention to these guidelines. Happy coding!

2.2 KiB Raw Permalink Blame History Unescape Escape