What problem does it solve?
Native MCP Client connects Titan Agent to external Model Context Protocol (MCP) servers so their tools are discovered and immediately usable as first-class agent tools, avoiding extra glue tooling or manual tool wiring.
Core Features & Use Cases
- Auto-discovered tool registry: On startup, connects to configured MCP servers and lists their tools for registration.
- Works with multiple transports: Supports local stdio MCP servers (command-based via npx/uvx) and remote HTTP MCP servers (URL-based).
- Collision-free naming: Registers tools with the pattern mcp_{server_name}_{tool_name}, making many servers usable together.
- Safety-oriented environment handling: Filters environment variables for stdio servers and supports explicit env pass-through only.
- Connection resilience and redaction: Retries failed connections with exponential backoff and redacts credential-like strings in errors.
Quick Start
Configure your MCP servers in ~/.Titan/config.yaml under mcp_servers, restart Titan Agent, then ask it to use an MCP tool like “get the current time from the time MCP server.”