Skip to content

MCP

LingXiao connects to external systems through the unified mcp tool entry, supporting three capability types: tools, resources, and prompts.

All MCP operations are performed through the mcp tool:

ActionDescription
list_serversList installed MCP servers
list_toolsList server-exposed tools
call_toolCall a server tool
list_resourcesList server resources
read_resourceRead a server resource
list_promptsList server prompts
get_promptGet a server prompt
list_resource_templatesList resource templates
capability_snapshotView server capability snapshot

MCP servers are configured via settings.mcp.servers:

{
"mcp": {
"servers": {
"filesystem": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/dir"],
"env": {}
}
}
}
}
{
"mcp": {
"servers": {
"remote-api": {
"url": "https://example.com/mcp",
"transport": "streamable-http"
}
}
}
}
Terminal window
# Add remote HTTP server
/mcp add-remote my-server https://example.com/mcp "My Server"
# Add stdio server
/mcp add-stdio my-server npx -y @modelcontextprotocol/server-filesystem /tmp

MCP Share supports importing/exporting MCP server configurations via share links and .mcpb bundles.

Generates portable share links containing the server’s complete configuration (sensitive info sanitized).

.mcpb is a portable packaging format for MCP servers, containing:

  • Server code or configuration
  • Dependency declarations
  • Metadata

When a plugin is enabled, its contributed MCP servers sync to settings.mcp.servers, accessible through the same mcp tool entry.

  • MCP tools registered to ToolRegistry can be called by Agents at runtime
  • MCP resources are read via read_resource
  • MCP prompts are obtained via get_prompt
  • All MCP operation artifacts, URIs, and validation results are written to work notes