Reference for the FrameworX MCP SDK, the surfaces it ships, and the tooling extension model.
AI Integration → MCP SDK Reference
|
New in 10.1.5. SDK upgraded to Anthropic MCP SDK 1.2.0. The runtime target is now .NET 10 (.NET 8 remains for 10.1.4 and earlier). |
The FrameworX MCP SDK is the .NET library Tatsoft uses to expose Designer and workspace tools to MCP clients (Claude Desktop, Claude Code, VS Code GitHub Copilot, any MCP-compatible LLM). It is layered on top of the Anthropic MCP SDK for .NET and ships as four compiled server executables, each targeting a specific workflow.
Setup steps are covered in MCP and Claude Setup and Claude Code MCP Setup. Tool-level reference lives in the dedicated pages listed below.
Server Surfaces
The SDK ships four servers. Each one is a distinct executable with its own process, transport, and tool surface.
| Server | Purpose | Transport | Executable |
|---|---|---|---|
| DesignerMCP | Live IDE co-pilot on the same Windows machine as Designer. | stdio | DesignerMCP.dll |
| DesignerMCPHttp | Live IDE co-pilot over HTTP, for split-host setups (Mac + Windows VM). | HTTP (SSE) on port 10150 | DesignerMCPHttp.dll |
| ConsoleMCP | File-based workspace engineering, no running Designer. | stdio | ConsoleMCP.dll |
| ConsoleMCPHttp | File-based workspace engineering over HTTP. | HTTP (SSE) on port 10130 | ConsoleMCPHttp.dll |
The HTTP servers add bearer-token authentication and DNS rebinding protection defaults suitable for Parallels-internal Mac-to-Windows networks. Use a reverse proxy if you expose the HTTP surface beyond a trusted subnet.
Runtime Requirements
| FrameworX version | Runtime | Install path |
|---|---|---|
| 10.1.4 and earlier | .NET 8 Desktop Runtime | C:\Program Files\Tatsoft\FrameworX\fx-10\net8.0\ |
| 10.1.5 and later | .NET 10 Desktop Runtime | C:\Program Files\Tatsoft\FrameworX\fx-10\net10.0\ |
Verify with dotnet --list-runtimes. A mismatched runtime surfaces as the server failing to start under Claude Desktop or Claude Code.
Transport Model
Every server speaks JSON-RPC 2.0 over its transport. The SDK framing rules follow the MCP 1.2 streamable-HTTP specification for the HTTP servers and the stdio specification for the stdio servers.
stdio servers
The MCP client spawns the server as a subprocess. stdin carries requests, stdout carries responses, stderr is reserved for logging. Environment variables set on the client process flow to the server.
HTTP servers
The server listens on its configured port. The client negotiates a session over POST /sse and then streams events over GET /sse. Authorization is Authorization: Bearer <token>. The token is configured in %APPDATA%\FrameworX\Mcp\config.json on first run.
Tool Reference
Each tool-level reference lives on its own page.
- ConsoleMCP Reference — file-based workspace tools.
- designer_action Reference — Designer visual and runtime control actions.
- AI Designer Connector — live Designer tools (shared between DesignerMCP and DesignerMCPHttp).
Extensibility
The SDK is NOT a public plug-in surface. Tools are compiled into the shipped executables and are not loaded from user-supplied assemblies. The extension path for customer-specific behavior is via Claude Skills (markdown playbooks loaded by the MCP client) and via search_docs, both of which run on top of the existing tool catalog.
For customer-specific automation via scripts and expressions, see Skill Scripts Expressions.
Version History
| FrameworX | Anthropic MCP SDK | Notes |
|---|---|---|
| 10.1.3 | 1.0 | Initial ship of DesignerMCP and DesignerMCPHttp. |
| 10.1.4 | 1.1 | ConsoleMCP and ConsoleMCPHttp added. |
| 10.1.5 | 1.2 | SDK bump to 1.2. Runtime moves to .NET 10. Workspace architecture v2 (*_workspace tool names, create_solution_file, update_solution_file, from_workspace parameter). |