MCP servers make selected Link functionality available to AI assistants and other applications through the Model Context Protocol (MCP).
Each server exposes tools with descriptions and structured input parameters. A compatible client can discover these tools and invoke them to retrieve information or perform defined operations.
What can you expose?
Tools can provide controlled access to searches, lookups, and business operations in Link or selected external systems. The available functionality is determined by the server’s artifact implementation.
Hosting and access
Link hosts the server and handles the MCP protocol, HTTP transport, routing, and configured authentication. Servers are configured under Transport > MCP servers.
Built-in authentication and user-group restrictions control access to the server. Each tool must enforce any additional permissions and business rules.
See API Authentication for authentication guidance.
This feature is currently in preview and may change before the final release.
Development guides
-
MCP Handlers (preview) — Tool implementation, metadata, server configuration, deployment, and testing.
-
How to develop Link 3 artifacts — General artifact development, configuration, and dependency injection.