Load MCP tools from your configured servers with a single function call, following the agent-centric design principles.Documentation Index
Fetch the complete documentation index at: https://docs.praison.ai/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
How It Works
The loader bridges configuration and agent setup by:- Reading configs from
~/.praisonai/mcp/directory - Filtering by enabled status and optional name selection
- Converting each config to an MCP client instance
- Returning ready-to-use tool instances
Configuration Options
| Parameter | Type | Default | Description |
|---|---|---|---|
names | List[str] | None | Specific config names to load (None = all enabled) |
configs | List[MCPConfig] | None | Optional injected configs from wrapper TOML loader |
prefix_tools | bool | True | Prefix tool names when multiple servers loaded (collision avoidance — currently stub) |
Common Patterns
Load All Enabled Servers
The simplest approach - load everything that’s enabled:Load Specific Servers
Target specific capabilities for focused agents:Inject Configs from TOML
Advanced usage with wrapper TOML loading:Best Practices
Configure Once, Use Everywhere
Configure Once, Use Everywhere
Set up your MCP servers once using
praisonai mcp create, then any agent can pick them up automatically via load_mcp_tools(). This follows the “configure once, use everywhere” principle.Filter by Purpose
Filter by Purpose
Use specific server names rather than loading everything. A file processing agent only needs
["filesystem"], while a development agent might need ["filesystem", "github", "postgres"].Handle Missing Configs Gracefully
Handle Missing Configs Gracefully
The loader silently skips disabled or missing configs. Always check that your expected servers are enabled with
praisonai mcp list.Tool Name Collision Awareness
Tool Name Collision Awareness
When loading multiple servers that might have overlapping tool names, be aware that
prefix_tools=True is currently a stub. Plan your server selection to avoid conflicts.Related
MCP Tool Filtering
Restrict which MCP tools an agent can see and call
MCP CLI
Configure and manage MCP servers from the command line

