Skip to main content
Recommended Reading: For practical implementation details, see the MCP Integration Guide.
💻 Code Examples

Basic MCP

Get started with MCP

Advanced MCP

Multiple servers & filtering

What is MCP?

The Model Context Protocol (MCP) is an open standard that enables seamless communication between AI applications and external tools. Slide’s Tyler package includes first-class MCP support, allowing your agents to:
  • Connect to any MCP-compatible server
  • Use tools from external services
  • Share context across applications
  • Build interoperable AI systems
Tyler follows the MCP 2025-11-25 stable transport framing: Streamable HTTP is the default for remote servers, stdio is for local subprocess servers, and SSE is legacy compatibility.

MCP Architecture in Slide

Tyler uses the official MCP SDK’s ClientSessionGroup to manage connections to multiple MCP servers simultaneously. This provides:
  • Automatic session lifecycle management
  • Tool discovery and aggregation across servers
  • Tool execution routing to the correct server
  • Standard MCP transports (stdio, Streamable HTTP) plus legacy SSE compatibility

Quick Start

Using MCP Tools

Once connected, MCP tools are automatically available to your agent with namespaced names:

MCP Server Types

1. Stdio Servers

Local processes that communicate via standard input/output. Great for local tools and development:

2. Streamable HTTP Servers

HTTP-based servers using the current remote transport. Recommended for hosted MCP servers:

3. SSE (Server-Sent Events) Servers

Legacy HTTP transport for backward compatibility with older MCP servers:

Creating MCP Servers

Using FastMCP (Python)

Create an MCP server that exposes tools to Slide:

Advanced MCP Usage

Multiple Server Connections

Connect to multiple MCP servers simultaneously:

Tool Filtering

Control which tools are available:

Custom Prefixes

Override the default namespace prefix for cleaner tool names:

Environment Variable Substitution

Use environment variables for secrets (recommended!):

Graceful Degradation

Control failure behavior per server:

Best Practices

Always cleanup MCP connections:
Never hardcode secrets:
Only connect to reviewed MCP servers. MCP tools execute with your agent’s permissions, local stdio servers run with the same privileges as Tyler, and tool annotations/metadata are advisory unless the server is trusted.
Use custom prefixes for cleaner tool names:
Use fail_silent: True for optional servers:

Troubleshooting

Common MCP issues and solutions:
  • Connection refused: Check if MCP server is running and URL is correct
  • Tool not found: Verify tool is exposed by server, check include_tools/exclude_tools
  • Timeout errors: Increase timeout or check network connectivity
  • Permission denied: Verify authentication credentials
  • Environment variable not substituted: Ensure variable is set before running

Next Steps

MCP Integration Guide

Detailed configuration reference

MCP Examples

See MCP integration examples

Create MCP Server

Build your own MCP server

MCP Specification

Read the MCP specification