Highlight community projects

オープン
#1,992 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp
領域
documentation

調査の方向性

Start with the repository README and documentation structure to find where community project listings and server guidance belong; the issue names no specific files or tests. Clarify whether the project wants a community list, guidance on identity and authorization, or both, and whether showcases belong in GitHub Discussions. Done means adding the agreed listing and/or concise guidance on host identity flow and authorization enforcement.

索引モデルが issue の本文から書いたものです。

説明

enhancement

Is your feature request related to a problem? Please describe.
I maintain Foundgine, an open-source semantic execution layer for .NET. I looked for a place in this repo or its docs where .NET community projects around MCP are listed, and couldn't find one, so developers have no obvious way to discover existing servers, adapters and tools. I'm also unsure what the recommended approach is for servers that expose application-level capabilities, where authorization and caller identity come from the host application rather than from the MCP layer.

Describe the solution you'd like

  1. A "Community projects" section in the README or docs, where .NET servers, adapters and tools can be listed with a short description and link.
  2. A short documentation page on conventions for identity and authorization when a server exposes application capabilities, for example how the host application's identity should flow into tool calls, and where authorization should be enforced.

I'm happy to open a pull request for either.

Describe alternatives you've considered

  • Listing projects only in the official MCP Registry. That helps discovery across languages, but not for people browsing the C# SDK repo.
  • Using GitHub Discussions on this repo for community showcases, if that is preferred over a docs page.
  • Documenting the approach only on each project's own docs site, which doesn't help people who never find it.

Additional context
Foundgine lets an application define its entities, fields, relationships and capabilities once. Every request is resolved against the semantic model, authorized using the identity supplied by the host application, bound into a provider-independent execution plan, and executed. The same rules apply to every caller, including AI agents, so authorization logic isn't duplicated per entry point.

主要言語
C#
スター
4.6k
フォーク
849
平均マージ
1日 16時間
マージ済み PR(30日)
24

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

modelcontextprotocol/csharp-sdk のほかの issue

modelcontextprotocol/csharp-sdk の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。