SysML-v2-API

The SysML v2 API MCP-Server provides an MCP-compliant interface to a SysML v2 model context. Designed as a C++-based server, it exposes resources and methods aligned with the SysML v2 API & Services specification, enabling AI models and agents to query and reason over a SysML v2 model context via MCP operations. This enables tools to fetch model information, perform model queries, and receive structured responses that can be used as contextual grounding for reasoning tasks. The server is modular by design to allow easy extension to additional MCP transport layers or HTTP clients as needed.

To use the server, run the container or binary (depending on your deployment choice) and connect to the MCP endpoint as defined by the MCP protocol. The server will provide MCP endpoints for model context requests, such as retrieving SysML v2 model elements, services, and relevant metadata. When integrated with an AI agent, you can issue MCP commands to fetch model context, resolve references, and obtain structured data suitable for reasoning, analysis, and plan generation within the SysML v2 domain.

Prerequisites:

• A supported environment with Docker installed (or a build environment for C++ if you prefer building from source).
• Basic familiarity with the MCP protocol and HTTP-based APIs.

Option A: Run via Docker

1. Ensure Docker is installed and running.
2. Pull and run the image (adjust image tag as needed): docker pull redsteve/sysml-v2-api-mcp-server:latest docker run -d --name sysml-v2-api-mcp -p 8080:8080 redsteve/sysml-v2-api-mcp-server:latest
3. The MCP endpoint will be available at the container's exposed port (e.g., http://localhost:8080).

Option B: Build from source (C++ source required)

1. Install prerequisites: a modern C++ compiler, CMake, and Git.
2. Clone the repository: git clone https://github.com/redsteve/sysml-v2-api-mcp-server.git cd sysml-v2-api-mcp-server
3. Create a build directory and configure: mkdir build && cd build cmake .. -DCMAKE_BUILD_TYPE=Release
4. Build the project: cmake --build . --config Release
5. Run the server (adjust path to the built executable as needed): ./sysml_v2_api_mcp_server
6. Ensure the server is reachable at the configured endpoint (default 8080 or as defined in the build/run configuration).

Notes:

• If environment variables are required by your deployment, set them before starting the server (for example, MCP_LOG_LEVEL or SYSML_API_ENDPOINT).
• Since the project is a work in progress, expect ongoing changes and potential breaking updates during development.

Tips and common issues:

• The project is marked as WORK IN PROGRESS; verify compatibility with your MCP client and SysML v2 API services before production use.
• If using Docker, ensure the host ports do not conflict with other services and that network access to the SysML v2 API endpoints is configured if the container needs to reach external services.
• Environment variables can be added to tune logging and external API endpoints. For example, MCP_LOG_LEVEL controls verbosity, and SYSML_API_ENDPOINT can point to the SysML v2 API services if the MCP server fetches model data remotely.
• When extending the server, the codebase is designed to support adding more MCP transport layers or HTTP clients; consider contributing via the repository if you implement additional capabilities.
• If you encounter build issues on Linux vs macOS, ensure you have the correct compiler toolchain and dependencies as indicated in the build scripts or CONTRIBUTING guidelines.