MCP Server

AI-Powered Asset Management with MCP

The Model Context Protocol (MCP) is an open standard that allows AI assistants to connect to external tools and data sources. The xAssets MCP Server is a free, open-source bridge between your xAssets instance and any MCP-compatible AI assistant — including Microsoft Copilot, Claude, ChatGPT, and others.

Instead of navigating menus and building queries manually, your team can ask questions in plain English and get answers directly from your asset data. The MCP server handles authentication, permissions, and data access through the xAssets API — your AI assistant never connects to the database directly.

What Can You Do With It?

• Query your assets in natural language — ask "show me all laptops assigned to the London office" and get results from your live data
• Run saved reports — execute any of your existing queries and reports through the AI assistant
• Browse your data model — explore categories, locations, departments, cost centres, menus, and field definitions
• Read and update asset records — view full asset detail and make changes with AI assistance
• Execute bulk operations — run transformations, disposals, and other specialised operations
• Get help and guidance — the AI assistant understands your xAssets configuration and can guide users through workflows

Available Tools

The MCP server exposes seven tools that cover the full range of day-to-day asset management operations:

• metadata — browse the data model including asset categories, locations, departments, cost centres, saved queries, transformations, menus, and field definitions
• query_run — run any saved query or report by name, with optional parameters
• record_read — read individual asset records or lists of records
• record_save — update asset records after modification
• api_command — execute any xAssets API command for operations not covered by the other tools
• save_special — run bulk operations such as asset disposal, transfer, or transformation execution
• explain — return help text describing available tools and common workflows

Security

The MCP server connects to xAssets through the REST API using API key authentication. All data access is mediated by the same user permissions model that applies to the web interface — the AI assistant can only see and do what the API key's user group allows. No direct database access is possible.

Administrators control exactly which user group and permission level each API key operates under.

Getting Started

The MCP server is a standalone .NET application that runs alongside your AI assistant. Setup takes a few minutes:

1. Download the MCP server from your xAssets instance or request it from support
2. Create an API key in xAssets (Admin > API Keys) with the appropriate permissions
3. Configure appsettings.json with your instance URL, API key, and database name
4. Point your AI assistant at the MCP server executable

The server communicates via the standard MCP JSON-RPC protocol over stdin/stdout, so it works with any MCP-compatible client without additional configuration.

Open Source

The xAssets MCP Server is open source. Customers can inspect the code, extend it with additional tools, or adapt it to their specific workflows. It requires .NET 9.0 and network access to your xAssets instance.

Common Workflows

Browse and query assets

Use metadata to explore your categories and saved queries, then query_run to execute a report. The AI assistant can interpret the results and answer follow-up questions about your data.

Read and update a record

Use record_read to retrieve an asset, ask the AI to make changes, then record_save to write the update back. The AI assistant can look up field names using metadata to ensure the correct XML tags are used.

Run a transformation

Use metadata to list available transformations, then save_special to execute one. This is useful for scheduled imports, data cleansing, and bulk updates.