Model Context Protocol (MCP) server exposing the Opc.Classic client surface so AI agents can browse OPC servers, read/write items, subscribe to data changes, query historical data, and consume events through chat.
Get Started
No framework information available.
README
Opc.Classic.Mcp
Opc.Classic.Mcp is the stdio Model Context Protocol server for Opc.Classic. It exposes the managed OPC Classic client stack as MCP tools so AI agents can discover servers, manage sessions, browse DA/AE/HDA models, read and write values, poll events and subscriptions, inspect Batch/Commands/Cpx metadata, manage DX configuration, use OPC Security, call XML-DA endpoints, and capture/decode OPC Classic DCOM traffic.
For the full user guide, architecture diagram, authentication notes, and client-specific setup snippets, see docs/mcp/README.md. For the current tool catalog, see docs\mcp\tools.md.
Install from NuGet
dotnet tool install --global Opc.Classic.Mcp
The installed command is:
opc-classic-mcp
Use that command in MCP clients that support stdio servers:
{
"mcpServers": {
"opc-classic": {
"command": "opc-classic-mcp"
}
}
}
MCP clients that support NuGet package acquisition can launch the package directly with dnx:
{
"servers": {
"opc-classic": {
"type": "stdio",
"command": "dnx",
"args": [
"Opc.Classic.Mcp",
"--version",
"<version>",
"--yes"
]
}
}
}
Run from source
dotnet run --project mcp\Opc.Classic.Mcp
A local MCP client can launch the source tree directly:
{
"servers": {
"opc-classic": {
"type": "stdio",
"command": "dotnet",
"args": [
"run",
"--project",
"mcp\\Opc.Classic.Mcp"
]
}
}
}
Package
dotnet pack mcp\Opc.Classic.Mcp\Opc.Classic.Mcp.csproj -c Release
The project is packaged as a .NET tool and MCP server package (<PackAsTool>true</PackAsTool>, <PackageType>McpServer</PackageType>, <ToolCommandName>opc-classic-mcp</ToolCommandName>).
Downloads by Version
Similar & Alternative Packages
Hand-picked matching NuGet libraries based on tags & ecosystem
Depended On By
Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.
Adoption Assessment
Assess this package against its supported frameworks, license, maintenance signals and dependency graph before making it a project standard.
Related Guides & Workflows
Learn how to evaluate, integrate, or audit this package in your .NET project.