xal v0.1.0

Model: gpt-5.6-sol

Working directory: ~/Projects/xal

> /mcp

# Xal and MCP servers

Xal can connect to Model Context Protocol servers and expose their tools, resources, and prompts to an agent session. Configure each server independently in Xal configuration using a local stdio command or a remote streamable HTTP URL. MCP capabilities remain separate from built-in plugins and from every other MCP integration.

Use MCP when a coding task needs an external system such as an issue tracker, design tool, cloud platform, database, or internal documentation service. Apply narrow permissions to imported tools, keep credentials outside committed project files, and verify a server's trust boundary before allowing mutating calls.

The [Xal integrations documentation](/docs/integrations) contains configuration shapes and transport guidance. Xal acts as an MCP client; the xal.sh domain does not currently host a public MCP endpoint. Agents looking for Xal developer interfaces should use the [public REST API](/developers), the [OpenAPI specification](/openapi.json), or the local plugin API instead of guessing an MCP server URL.