Operate Xytech through an MCP server — orders, media workflows, scheduling, transmission, timecards, and invoicing — with OAuth access scoped to the individual tool level.
The X2 MCP server exposes Xytech's operational surface to autonomous agents and any MCP-compatible client — orders, media workflows, resource scheduling, transmission, timecards, and invoicing — through structured tools governed by OAuth with permission scoping at the individual tool level.
Access model: OAuth 2.1 (Authorization Code + PKCE). Your Xytech administrator grants each agent identity access to a specific set of tools. An agent granted xytech_search_orders but not xytech_create_order can read but never write. All tool invocations are audited.
Connect
Server URL (production)
https://mcp.xytech.fabricdata.com/mcp
Health
https://mcp.xytech.fabricdata.com/health
The server publishes standard discovery documents, so MCP clients configure themselves automatically:
Authentication is interactive: agents complete a browser-based OAuth consent to obtain a token. (A headless client-credentials/service-account flow is not currently offered.)
Claude / Claude Code:
Any MCP-compatible client (agent frameworks, IDEs, orchestration platforms) connects the same way: register the server URL, complete OAuth, discover tools.
Tools are organized by operational lifecycle area.
Goal: instantiate a media order for an image-ingest workflow and confirm resource availability.
Tools return structured errors with actionable messages; validation failures identify the offending field.
Read tools (get_*, search_*, list_*) are safe to retry. For write tools, re-read state with the corresponding get_*/search_* tool before retrying, to avoid duplicate creation — the server does not deduplicate writes via idempotency keys.
Tool-level OAuth scoping — grants map to Xytech's RBAC model; agents hold exactly the authority an administrator assigns.
Audit — every invocation is logged against the agent identity.
Environments — production (mcp.xytech.fabricdata.com) and staging (mcp.fox.stg.xytech.fabricdata.com
— machine-readable schemas, migration guide
— event-driven workflows instead of polling
— full markdown documentation index
Protected Resource Metadata
/.well-known/oauth-protected-resource
OpenID Configuration
/.well-known/openid-configuration
·
xytech_search_employee_contracts
·
xytech_run_personnel_rule_check
·
xytech_list_personnel_rule_sets
·
xytech_get_personnel_rule_set
·
xytech_list_personnel_rule_categories
·
xytech_get_personnel_rule_category
·
xytech_list_payroll_rules
·
xytech_get_payroll_rule
·
xytech_list_payroll_types
·
xytech_list_penalty_types
·
xytech_get_penalty_type
·
xytech_list_unions
·
xytech_get_union
·
xytech_list_union_rules
·
xytech_get_union_rule
·
xytech_list_qualifications
·
xytech_get_qualification
·
xytech_list_qualification_groups
The server exposes a /health endpoint and the xytech_healthcheck tool for connectivity and liveness checks.
) are provisioned separately; agent integrations are typically validated against staging first. Contact your Fabric account team for provisioning.
Transport
Streamable HTTP
Auth
OAuth 2.1 — Authorization Code grant with PKCE (S256). Dynamic Client Registration supported.
claude mcp add xytech-x2 https://mcp.xytech.fabricdata.com/mcp --transport http
# Complete the OAuth prompt in your browser; tool availability reflects your grants.
1. xytech_healthcheck → verify connectivity
2. xytech_search_customers {name: "..."} → resolve customer ID
3. xytech_create_media_order {...} → instantiate the order
4. xytech_check_resource_availability {...} → confirm ingest capacity
5. xytech_get_media_order_details {id} → verify state