MCP Endpoint — Connect External AI Tools
New 7.4.0
External MCP clients such as VS Code, Claude Desktop, Cline, and custom tools use the Nodinite MCP Endpoint to query your environment outside the Nodinite Web Client. The external MCP setup is required for every external client, regardless of whether you want general Repository Model discovery, Architecture Diagrams and Diagram Sets, Mermaid C4 output, or BizTalk Application analysis.
- Use the same external MCP setup for Repository, C4, and BizTalk questions
- Connect tools such as VS Code, Claude Desktop, and Cline to one Nodinite environment
- Explore Custom Metadata, relationships, Architecture Diagrams, and BizTalk content from one endpoint
- Keep the Web Client AI experience separate from external MCP client registration
Important
The external MCP setup is separate from the AI System Parameter.
EnableMcpChatandEnableDiagramAiAssistancecontrol in-product AI surfaces in the Nodinite Web Client. They do not register an external MCP client. For BizTalk-specific MCP tools,EnableAiForBizTalkmust also be enabled in the environment.
When External MCP Setup Is Required
| Scenario | Do you need external MCP setup? | Why |
|---|---|---|
| AI Assistant in the Nodinite Web Client | No | This is the in-product chat experience controlled by AI System Parameter and AI Assistant. |
| AI Assistance tab in Diagram Assistance | No | This is the in-product diagram AI experience controlled by EnableDiagramAiAssistance. |
| VS Code, Claude Desktop, Cline, or a custom MCP client | Yes | Every external client must register nodinite-mcp before it can query Nodinite. |
This is the most important rule to remember: if the user works outside the Nodinite Web Client, the external MCP setup is always required.
What You Can Use It For
Once connected, an external MCP client can be used across these major areas:
| Area | What users usually ask | Typical outcome |
|---|---|---|
| Repository Model | Which integrations are tagged as Critical? | Entity details, relationships, Domains, and Custom Metadata |
| Architecture Diagrams | Which systems in this Diagram Set still lack an L2 Container view? | Architecture Diagrams, Diagram Sets, Coverage, and review questions |
| BizTalk | Show me the BizTalk Application that owns these send ports | BizTalk Application discovery, artifact inspection, runtime analysis, and architecture generation |
The same client setup supports all three areas. You do not need one MCP configuration for Repository questions and another for BizTalk or C4 questions.
For BizTalk-specific MCP capabilities, the external client setup is only one part of the story. The environment must also have EnableAiForBizTalk enabled, and the caller must have the required administrator-level access.
How External MCP Access Works
Diagram: An external AI client reads its MCP configuration, connects to nodinite-mcp, and can then ask questions across the Repository Model, Architecture Diagrams, Diagram Sets, Mermaid C4 output, and BizTalk Application analysis.
Setup Summary
The exact syntax varies by client, but the setup model stays the same:
| Step | What you configure | Why it matters |
|---|---|---|
| 1 | Register nodinite-mcp in mcp.json or the equivalent client file |
Without client registration, the external tool cannot see Nodinite tools |
| 2 | Launch Nodinite.Core.McpServer through dnx |
This is the released MCP server package used by the client |
| 3 | Provide ConnectionStrings__NodiniteConfig and the client-specific values your environment needs |
The endpoint must be able to reach Nodinite_Config |
| 4 | Reload the client and validate with a simple question | Confirm connectivity before relying on more advanced queries |
For a detailed setup walkthrough, see Set up AI Assistant and MCP Endpoint.
Good First Questions
Start with simple, observable questions before you move to larger workflows:
- Show me all Applications in Production
- Which integrations are tagged as Gold?
- Which systems in the Order-to-Cash Diagram Set still lack an L2 Container diagram?
- List the send ports and receive locations in the OrderProcessing BizTalk Application
- Generate Mermaid C4 for the BizTalk application that handles invoices
These quick checks tell you whether the client can reach the right environment and whether the expected data is available.
Security and Expectations
External MCP access follows the same broad governance model as the rest of Nodinite.
- Access follows your environment permissions and role-based visibility.
- The endpoint is read-oriented and designed for discovery, explanation, and analysis.
- Do not commit real secrets in
mcp.jsonor the equivalent client configuration. - Review the data-handling model of the external AI client you choose, because that client decides where prompts and responses are processed.
Troubleshooting Checks
The client loads but no Nodinite tools appear
Verify that nodinite-mcp is registered inside the client's MCP configuration and reload the client after saving the file.
Repository questions work, but BizTalk or Architecture Diagram questions do not
Confirm that the environment actually contains the expected Architecture Diagrams, Diagram Sets, or BizTalk Application data and that the connected user can access it. For BizTalk-specific tools, also verify that EnableAiForBizTalk is enabled; otherwise the BizTalk capability remains unavailable even though the client itself is connected correctly.
The client starts but cannot read data
Review the values used for ConnectionStrings__NodiniteConfig, the package source, and any client-specific startup requirements.