Highlight community projects

Abierto
#1,992 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C#
Estrellas
4.6k
Forks
849
Merge medio
1 d 16 h
PR fusionados (30 d)
24

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de modelcontextprotocol/csharp-sdk

Todos los issues de modelcontextprotocol/csharp-sdk

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.