The SystemWeaver MCP Server connects AI assistants to a SystemWeaver model. It implements the Model Context Protocol (MCP), so any MCP-capable client, such as Claude Desktop or Claude Code, can navigate, read and, where you allow it, change SystemWeaver content through natural-language conversation.
The server runs locally on Windows and communicates with your existing SystemWeaver broker through the SystemWeaver ClientAPI. It acts with the permissions of the SystemWeaver user it connects as, so the AI assistant can see and do only what that user can.
Tools
The server provides 46 tools, grouped into capability areas. Each area can be turned on or off independently. Tools in a disabled area are not offered to the AI assistant, and any call to them is refused.
| Area | Default | What it covers |
|---|---|---|
| Navigate | On | Walk the item and part structure below an item (sw_walk). Find items by type, in the whole model or below a root item, and resolve an old version to its current version (sw_find). |
| Read | On | Read an item's name, type, description, attributes and, optionally, notes (sw_read). Read a full attribute value (sw_read_attribute). Read the attributes on a part link (sw_read_part_attributes). List and download attachments (sw_attachment_list, sw_attachment_download). |
| Describe | On | Explore the metamodel: list item types, show the parts and attributes of a type, and search item, part and attribute types (sw_types, sw_type, sw_search_metamodel). |
| Version read | On | Show an item's version history (sw_version_history) and find where an item is used (sw_references). |
| Config read | On | Read application configurations and configuration items (sw_config_list, sw_config_read, sw_config_item_read). Read view definitions such as grids, graphs and reports (sw_view_types, sw_view_list, sw_view_read). |
| Issue read | On | Read issue-management metadata (sw_issue_meta). Find users (sw_issue_user_find). Find issues by ID, project, linked item, status, assignee or text (sw_issue_find). Read an issue (sw_issue_read). |
| Help | On | Search and read the bundled SystemWeaver help (sw_help_search, sw_help_read). Works fully offline. |
| Item write | Off* | Create, update and delete items in bulk (sw_create_items, sw_update_items, sw_delete_items). Create and delete parts (sw_create_parts, sw_delete_parts). Set part attributes (sw_set_part_attributes). Add, edit and delete notes (sw_note_*). Add attachments (sw_attachment_add). |
| Version write | Off | Change an item's status, including release (sw_set_status), and create a new version (sw_new_version). |
| Issue write | Off | Create, update and delete issues (sw_issue_create, sw_issue_update, sw_issue_delete), and link issues to model items (sw_issue_link). |
| App config write | Off | Write an application configuration and turn it on or off (sw_config_set, sw_config_set_active). |
| Config item write | Off | Create configuration items and views, and set view definitions (sw_config_create_item, sw_view_create, sw_view_set_definition). |
| Server info | Always on | mcp_server_info shows the server version, the connected broker and user, the login method, the connection status and the licence state. It never returns secrets. |
* All write areas are off by default. The example configuration shipped with the server turns on Item write only.
Features
- Built for AI assistants. Responses are compact and projectable: you choose which fields to return, and long descriptions and attribute values are truncated at a configurable limit (the full value can still be requested). Bulk operations have a per-call limit. Errors are typed and tell the assistant what to do next, for example to create a new version when an item cannot be edited.
- Version-aware. Released items are protected. The tools guide the assistant to create new versions rather than change released content, and they resolve historic handles to the current version.
- Licence-controlled. The full tool set is available only when the connected user's SystemWeaver licence includes the MCP Server. Without it, only
mcp_server_infois available, and it reports why. Licence changes take effect without restarting the server. - Secure credential handling. Broker connection details and passwords are never stored in configuration files. You enter them once in the SystemWeaverMCP Credential Tool, which tests the login before saving and stores the details encrypted with Windows DPAPI for the current Windows user. If the stored data is missing, corrupt or belongs to another user, the server refuses to connect (fail-closed).
- Login methods. SystemWeaver login, network credentials, integrated Windows authentication and Microsoft Entra ID.
- Robust operation. Every broker operation has a timeout, and the size of inbound messages is limited. Proxy support is included. Logs are written to stderr so they never interfere with the protocol.
- Diagnostics. The
--testmode checks the credentials and the broker connection without an MCP client.