Shift config of "known-sdks.ts" to SDK-side config file
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by reading known-sdks.ts and the conformance runner's current options-handling path; the issue proposes moving SDK-specific settings into an SDK-side conformance.yaml while keeping the SDK map in this repository. Compare the proposed build, client, server, expectedFailures, and specOverrides fields with the current configuration, and consider how existing baseline.yml handling is affected. Done means the runner can obtain these settings from the checked-out SDK without requiring cross-repository configuration changes.
Written by the indexing model from the issue text.
Description
I really like the idea of easing the options handling and execution of the conformance runner, but immediately fell into the pitfall that this requires cross repo PRs and also decouples the versioning a bit inconvenient if changes are needed.
of course the sdk map would stay in this repo, but after checkout it could check for a conformance.yaml with the relevant settings:
# modelcontextprotocol/go-sdk
# conformance.yaml
build: 'go build -o ./.conformance-server ./conformance/everything-server && go build -o ./.conformance-client ./conformance/everything-client'
client:
command: './.conformance-client'
server:
command: './.conformance-server -http=localhost:3000 -stateless=false'
url: 'http://localhost:3000'
expectedFailures: 'conformance/baseline.yml'
specOverrides:
'2026-07-28':
server: { command: './.conformance-server -http=localhost:3000' }
WDYT?
- Dominant language
- TypeScript
- Stars
- 127
- Forks
- 101
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 6
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/conformance
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
modelcontextprotocol/conformance#315 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/conformance#312 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 40/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
All issues in modelcontextprotocol/conformance
Similar issues
-
VerificationGate: ATTRIBUTION quote guard never matches a normal quotation (\b around the quote) Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2234 ·
-
T: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100