← Registry tracker
Claude Connector

Softhills Product Documentation

Search Softhills 3D visualization SDK documentation — VIZCore3D.NET, VIZCore3DX.NET, VIZWide3D and more — with exact API signatures instead of guesses.

View in the Claude registry
Brand
Unknown
Category
Pending
Primary Subcategory
Pending
Integration details

Description

Softhills builds 3D visualization SDKs used in shipbuilding, plant engineering, and manufacturing — large-model viewers, clash detection, 2D/3D conversion, and web visualization components for .NET and the browser. These libraries are not in any general model's training data. Ask about VIZCore3DX.NET and a model will produce plausible-looking code against an API that does not exist. This connector removes the guessing by giving Claude the actual published documentation. WHAT IT SEARCHES 30,000+ documents covering 14 products, indexed from the official documentation site at docs.softhills.net: - VIZCore3DX.NET, VIZCore3D.NET, VIZCore3D+.NET — large-model 3D viewers for .NET - VIZZARD, VIZZARDX — 3D model visualization and editing - VIZCore3DX.Core (ShdCore.NET) — lightweight .viz/.vizx format library, versioned - VIZWide3D, VIZWeb3D, VIZWeb2D — browser-based visualization, no plugin - VIZWing — Android 3D viewer - VIZPub, VIZPub 2D — CAD to lightweight format conversion - VIZDesign, VIZCLASH.NET — multi-CAD assembly, clash detection - Setup and support notes — graphics card requirements, redistributables, downloads Reference documentation, guides, release notes, and example code from the public repositories are all included. WHAT YOU CAN ASK - "How do I open a .viz model in VIZCore3DX?" - "What members does RibbonControl expose in VIZCore3DX.NET?" - "Show me an example of clash detection in VIZCore3DX.NET" - "What are the graphics card requirements for running the viewer?" Beyond plain search, the connector can list the API members of a class, pull code examples, browse a document's sections, search by tag, and find documents related to one you are already reading. Versioned products can be queried at a specific version, or left unspecified to get the latest. WHO IT IS FOR Developers integrating Softhills SDKs. No account, no sign-in, no API key — connect and ask. The documentation it serves is already public.

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Pending

The broad Category that contains the Primary Subcategory.

Primary Subcategory
Pending

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Brand
Unknown
Access
No account required
First tracked
2026-09-30
Tool count
12
Geography
US
Agent DiscoverabilityClaude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Softhills Product Documentation has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.
Tools

12 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

Softhills Product Documentation FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve a Community connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.