Highlight community projects
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- csharp
调研方向
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 内容生成。
描述
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
- A "Community projects" section in the README or docs, where .NET servers, adapters and tools can be listed with a short description and link.
- 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 小时
- 30 天内合并 PR
- 24
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
modelcontextprotocol/csharp-sdk 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 88/100
modelcontextprotocol/csharp-sdk#2031 ·
维护者通常 1 天内回复
-
Static resources whose URIs differ only in the fragment or user info collapse into one可能已有人在做 @halter73 于 9 天前认领。 未关闭P2
难度 2/5 1-3 小时 新手友好度 78/100
modelcontextprotocol/csharp-sdk#1970 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
POST /mcp with a missing or unparseable Content-Type returns HTTP 500 instead of a 4xx可能已有人在做 @halter73 于 9 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
modelcontextprotocol/csharp-sdk#1966 · 5 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Reserved URI-template expansion throws for supplementary Unicode characters可能已有人在做 @tarekgh 于 2 天前认领。 未关闭P3
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/csharp-sdk#1913 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
ClaimsPrincipal parameter injection sample request可能已有人在做 @utsavjain2809 于 48 天前认领。 未关闭help wanted P3
难度 2/5 1-3 小时 新手友好度 74/100
modelcontextprotocol/csharp-sdk#1899 ·
维护者通常 1 天内回复
查看 modelcontextprotocol/csharp-sdk 的全部 Issue
相似的 Issue
-
account bug effort:S P2
难度 2/5 1-3 小时 新手友好度 78/100
nightscout/nocturne#3745 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
grate-devs/grate#969 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
jsboige/CoursIA#27768 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
martin-stromberg/FinanceManager#562 ·
维护者通常 1 天内回复