Highlight community projects

Aberta
#1,992 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
csharp
Domínio
documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
4.6k
Forks
849
Merge médio
1d 16h
PRs com merge (30d)
24

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de modelcontextprotocol/csharp-sdk

Todas as issues de modelcontextprotocol/csharp-sdk

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.