modelcontextprotocol / modelcontextprotocol/conformance

Add JSON-based setup option to authorization server conformance test

Open
#225 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
127
Forks
101
Avg merge
6d 1h
Merged PRs (30d)
7

Description

Background

In the future, conformance test for authorization server requires many options such as url, client_id, client_secret, redirect_uri.

Solution

Conformance test for authorization server provides the following setup options so that testers can choose their preferred setup option. The number is priority of the options. However, options unrelated to the authorization server, such as outputDir and specVersion, are not covered from these setup options.

  1. command options
  2. json file option
  3. default value

For Example

In the following case, http://auth1.example.com, which is set in url option, will be used.

npx @modelcontextprotocol/conformance authorization --file autorization-server-settings.json --url http://auth1.example.com

In the following case, http://auth2.example.com, which is set in autorization-server-settings.json, will be used.

npx @modelcontextprotocol/conformance authorization --file autorization-server-settings.json

autorization-server-settings.json

{
  "url": "http://auth2.example.com"
}

In the following case, conformance test for authorization server occures error.

npx @modelcontextprotocol/conformance authorization

Contributor guide

Open the contributing guide

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.

Research direction

Start from the authorization conformance-test command and its existing command-option handling. Add the JSON setup option with command options taking precedence over JSON values and defaults, and preserve errors when required authorization-server settings are absent; verify the three example invocation cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authorization, testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.