[Shouryamaan Jain (shouryamaanjain)]

Adds Cohesivity to the Python and .NET community-project catalogs, under Tools. It is the first entry on the .NET page and sits in alphabetical order on the Python page.

• Project: public repository https://github.com/cohesivity-org/cohesivity-mcp (MIT); the integration guide is the README section at https://github.com/cohesivity-org/cohesivity-mcp#microsoft-agent-framework.
• Published: yes, for both SDKs. The guide shows a Python Agent with MCPStreamableHTTPTool and a .NET agent with McpClient tools, both pointed at https://cohesivity.ai/mcp, which needs no token. Both were run against the live server (agent-framework 1.21.0; Microsoft.Agents.AI.OpenAI 1.25.0 with ModelContextProtocol 2.2.0) with the model's tool calls scripted: the agent loaded the six tools, created a tenant and provisioned Postgres.
• SDK: Python and .NET, with the same row on both pages.
• Issues: https://github.com/cohesivity-org/cohesivity-mcp/issues/new/choose
• The row uses neutral wording and claims no Microsoft ownership, endorsement, testing or support.

This change was prepared with an AI coding agent.

---

Disclosure: I work at Cohesivity, which operates this MCP server.

[Copilot]

🔵 Needs a closer look

Local catalog checks pass, but the required Markdown link-check result remains unverified.

0 open findings

What changed in this PR

Adds Cohesivity to the Python and .NET community-project catalogs as an external MCP tool integration.

Changes:

• Adds matching entries with integration documentation and issue-creation links.
• Creates the .NET Tools section and preserves alphabetical ordering in Python.

File	Description
python/​samples/​community-projects.md	Adds Cohesivity under Tools before Engram.
dotnet/​samples/​community-projects.md	Replaces the empty catalog placeholder with a Tools table containing Cohesivity.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[Shouryamaan Jain (shouryamaanjain)]

@microsoft-github-policy-service agree company="Cohesivity"

[Eduard van Valkenburg (eavanvalkenburg)]

We've update the guidance about what we want in the community contributions, and examples of just using the built-in constructs, like this one, are not the intent, the intent is for packages/projects that actually implement some of our abstractions, for the same reason generic Otel compatible tools are also not accepted. It is great to see our code in your docs, thanks for including that!