Quick Start
1
Install MCP Support
2
Connect to MCP Server
Transport Types
| Transport | URL Pattern | Use Case |
|---|---|---|
| stdio | Command string | Local subprocess servers |
| SSE | http://.../sse | Legacy HTTP+SSE servers |
| HTTP Stream | http://... | Modern HTTP servers |
| WebSocket | ws://... or wss://... | Real-time bidirectional |
Connection Methods
Stdio (Subprocess)
HTTP/SSE
WebSocket
Configuration Options
| Option | Type | Default | Description |
|---|---|---|---|
command_or_string | str | Required | Command, URL, or command string |
args | list | None | Arguments for stdio transport |
timeout | int | 60 | Timeout in seconds |
debug | bool | False | Enable debug logging |
auth_token | str | None | Authentication token (WebSocket) |
How It Works
Tool Discovery
MCP automatically discovers tools from the server:Tool Execution
Tools are executed through the MCP protocol:Creating MCP Servers
Expose your tools as an MCP server:Common Patterns
NPX Servers (Smithery)
Multi-Server Setup
Best Practices
Use appropriate transport
Use appropriate transport
- stdio: Best for local tools, simple setup
- HTTP Stream: Best for remote servers, modern standard
- WebSocket: Best for real-time, bidirectional communication
Set reasonable timeouts
Set reasonable timeouts
Increase timeout for slow-starting servers or network latency.
Enable debug for troubleshooting
Enable debug for troubleshooting
Use
debug=True to see MCP protocol messages when debugging.Handle server availability
Handle server availability
MCP servers may not always be available. Handle initialization failures gracefully.

