okf-mcp: serve a bundle from S3 through the S3 bundle provider

Open
#238 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
22/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, csharp
Domain
cli, cloud

Research direction

Start in src/OKF4net.Mcp/ and read OkfMcpConfig, where the bundle root is resolved today, and the composition root that wires the bundle handle. The S3 provider from #142 must exist first, so check whether it has landed. Done means the S3 options are parsed with a one-line stderr error and non-zero exit on bad input, and the server serves the bundle read-only with the chosen refresh policy.

Written by the indexing model from the issue text.

Description

.NET enhancement

Area

src/OKF4net.Mcp/ (okf-mcp dotnet tool): let the MCP server serve a bundle stored in S3 / an S3-compatible store, through the S3 bundle provider of #142.

Why it matters

#142 delivers the provider as a library only. A user of okf-mcp today can only point it at a local directory; serving a shared, remotely managed bundle to an MCP client is the stated goal of the provider work.

Scope

  • Command-line / configuration options naming the S3 source (bucket, key prefix, region, endpoint, addressing style), resolved by OkfMcpConfig like the bundle root today; a misconfiguration prints a one-line error to stderr and exits non-zero.
  • Credentials: okf-mcp is a leaf executable, so it may opt into the client library's default credential chain in its own composition root (security framing on #139, 2026-10-06, §3); the provider itself still never reads a secret. Document which sources the chain reads.
  • The provider is asynchronous (CompletesSynchronously = false) and read-only: the server serves it through a BundleHandle with a refresh policy to choose (OnAccess or Every), and offers no write tool.
  • Dependency weight: okf-mcp gains the S3 provider package and whatever client library #142 settles on (decision D1 of its spec); measure the tool package before/after.
  • stdio invariant unchanged: every log line (including the client library's) goes to stderr.

Out of scope

The catalog factory for S3 sources.

Depends on

#142

Effort

M

Dominant language
C#
Stars
4
Forks
1
Avg merge
1d 4h
Merged PRs (30d)
32

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jchable/okf4net

All issues in jchable/okf4net

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.