- 3 minutes to read

MCP Endpoint — Connect External AI Tools

New 7.x

Nodinite exposes a Model Context Protocol (MCP) endpoint that allows external AI tools to query your integration data directly — without switching to the Nodinite web portal. Connect Claude Desktop, Cline, VS Code, Zed, or any MCP-compatible client once and access your entire Nodinite landscape from inside your existing AI workflow.

The MCP endpoint is available, but detailed configuration documentation for external clients is still being finalized. Contact Nodinite support for early access guidance.


What is MCP?

The Model Context Protocol (MCP) is an open standard developed by Anthropic that allows AI assistants to connect to external data sources and tools. Think of it as "API for AI" — instead of you writing API calls, your AI assistant can discover and use Nodinite's capabilities automatically.

Why use the MCP endpoint with Nodinite:

  • Universal compatibility — Works with any MCP-compatible AI client (Claude Desktop, Cline, Zed, custom tools)
  • Multi-tool workflows — Combine Nodinite data with filesystem access, web search, and other MCP servers in one conversation
  • Developer-friendly — Query Nodinite environments while coding in VS Code or other development tools
  • Automation potential — Build custom AI workflows that react to Nodinite monitoring events

Available MCP Capabilities

Once connected, external AI tools can access these Nodinite capabilities:

Capability Purpose Example Query
Search Entities Find entities by name, type, or domain "Find all SAP integrations"
Get Entity Details Retrieve full configuration for an entity "Show me details for the Finance API endpoint"
List Relationships Discover dependencies and connections "What endpoints depend on our Payment Gateway?"
Query Custom Metadata Search by business attributes "Which integrations are tagged as 'Critical'?"
Get Domain Hierarchy Understand organizational structure "Show me the Finance domain structure"

The AI client automatically selects the right capabilities based on your question.


Connecting External AI Tools

Note

Configuration documentation coming soon. The MCP endpoint is available in Nodinite, but detailed setup instructions for external clients (Claude Desktop, Cline, VS Code, etc.) are still being finalized. This section will be updated with:

  • Authentication and API endpoint details
  • Configuration examples for popular MCP clients
  • Step-by-step connection guides

Check back for updates or contact Nodinite support for early access guidance.


Security & Access Control

All MCP connections use Nodinite's standard authentication and role-based access control — the same permissions model as the Web API. Users connecting via MCP only see data they are authorized to access.

  • Authentication: API keys with the same role-based access control as the Nodinite Web API
  • Data scope: Read-only access to Repository Model (Entities, Relationships, Custom Metadata)
  • Audit trail: All AI queries via MCP are logged in Nodinite audit logs

Next Step

AI Assistant — integrated chat interface and provider configuration

AI Assistant
AI Diagnostics
Repository Model
Web API