Third-party Notice
Last updated 2026-09-01
This notice explains what DCCMCP does, how we relate to the software vendors whose applications we connect to, and how we handle open-source components. The short version: we write MCP integration software. We do not make, sell, license or support the host applications themselves, and we are not affiliated with any vendor or project we interoperate with.
1. What we do, and what we do not do
DCCMCP builds MCP (Model Context Protocol) servers, plugins and adapters. Our software is an integration layer: it lets an AI agent call tools inside a host application that you have installed and licensed yourself.
We do not develop, own, distribute, license, host or provide technical support for those host applications, and we do not modify them. When something goes wrong inside Blender, Maya, Houdini, Photoshop, QGIS or any other host application, the vendor or project that maintains it is the correct place to look — we support the integration layer.
- We write and support the MCP integration only.
- The host application remains the property and responsibility of its vendor or project.
- Your license for the host application is unaffected by installing our integration.
2. No affiliation, endorsement or sponsorship
DCCMCP is an independent product. We are not affiliated with, endorsed by, sponsored by, certified by or otherwise connected to any vendor or project whose software we interoperate with.
Where we name a product, we do so to describe compatibility. The companies and projects listed here are examples, not a complete list — the same position applies to every other vendor, project or product mentioned anywhere on this site, and to software we integrate with in future.
- Autodesk (Maya, 3ds Max, Revit, Civil 3D)
- Adobe (Photoshop)
- Maxon (ZBrush)
- The Blender Foundation (Blender)
- Robert McNeel & Associates (Rhino, Grasshopper)
- The FreeCAD project
- The QGIS project
- The OpenCV project
- Every other vendor, project or product named on this site
3. Why we name other products
Software names are used descriptively to identify which applications an integration connects to, and to describe compatibility — nothing implies an official relationship. All product names, marks and logos remain the property of their respective owners, and any use on this site is for identification and compatibility purposes only.
4. Brand marks and where they come from
The client marks shown in our "supported agents" lists come from the LobeHub Icons collection (https://github.com/lobehub/lobe-icons), which is distributed under the MIT license. That license covers the artwork files; it does not grant trademark rights, which remain with each brand owner.
We render those marks unmodified apart from color — a single accent color, no distortion, no addition of our own branding — and only to indicate that the named client can connect to our MCP servers. Their appearance does not imply partnership, endorsement, sponsorship or certification by the brand owner.
Icons for host applications (Blender, Maya, Houdini, 3ds Max, Rhino, ZBrush, Photoshop, FreeCAD, QGIS, OpenCV) are our own abstract glyphs rather than vendor artwork. Where we do not have a client mark on file, we show a generic agent glyph instead.
Rights holders can ask us to correct or remove a mark at any time — see the corrections section below.
5. Your license obligations
Connecting an agent to a host application does not change the licensing terms of that application. You remain responsible for ensuring your use — including unattended, batch or server-side execution — complies with the vendor's license.
6. Open-source components
Our products may include open-source libraries. Required attributions, license texts and notices are included with each release and documented in the accompanying NOTICE file. Where we use open-source components, we do so under the terms of their licenses. The agent brand marks vendored from LobeHub Icons remain under the MIT license of that project, with attribution retained in our source.
7. Corrections
If you are a rights holder and believe we have described your product or used a mark incorrectly, contact support@dccmcp.com and we will correct or remove the reference promptly.
This document is a plain-language baseline written for technical review and is not legal advice. Enterprise order forms, a DPA and negotiated terms take precedence where they apply. Questions: support@dccmcp.com.