Remote MCP server should return client secret reference for configuration editing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
When an MCP server uses a client secret for authentication, the configuration response doesn’t include the client secret reference. This prevents proper editing of the server configuration since the reference is needed to preserve authentication.
Expected Behavior:
The configuration response should include the client secret reference so edits can be made without breaking authentication.
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.
Research direction
Locate the remote MCP server configuration response and the client-secret authentication handling. Trace how configuration editing preserves authentication, then include the client secret reference in the response and verify that editing a configured server does not break authentication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100