Highlight community projects

Offen
#1,992 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
45/100
Issue-Typ
Dokumentation
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp
Bereich
documentation

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
C#
Sterne
4.6k
Forks
849
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
24

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus modelcontextprotocol/csharp-sdk

Alle Issues in modelcontextprotocol/csharp-sdk

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.