MCP (Model Context Protocol)

MCP is an open protocol that lets you connect virtually any external tool or API to Stilla. If a service provides an MCP server, Stilla can use it — no custom integration required.

What MCP is

The Model Context Protocol is a standard for connecting AI systems to external tools. Instead of building bespoke integrations for every service, MCP provides a universal interface that any tool can implement.

For Stilla, this means the list of tools you can connect is effectively unlimited.

How it works

MCP servers are encapsulated as subagents within Stilla. Each MCP connection gets its own isolated agent with access to that server's tools. When Stilla needs to interact with an MCP-connected service, it delegates to the appropriate subagent.

Transport

Stilla supports remote MCP servers using the Streamable HTTP transport. MCP servers must be accessible via HTTPS.

Authorization

MCP connections support multiple authorization methods:

• Custom headers: Add API keys or tokens as HTTP headers
• OAuth: Full OAuth 2.0 authorization flow for services that require it

Stilla handles the complete OAuth flow, including token refresh.

Curated registry

Stilla maintains a curated list of verified MCP servers you can connect with one click:

• PagerDuty: Incident management, on-call schedules, service health
• PostHog: Product analytics, feature flags, experiments
• Polar: Open-source funding and subscription management
• And more being added regularly

Browse the full registry at stilla.ai/integrations.

Custom MCP servers

Connect any MCP-compatible server by providing its URL:

1. Go to Settings → Account → Connections
2. Select "Add MCP Server"
3. Enter the server URL
4. Configure authorization (headers or OAuth)
5. Stilla discovers available tools automatically

Building MCP servers

If you maintain an internal tool or API, you can build an MCP server for it and connect it to Stilla. The MCP specification is open and documented at modelcontextprotocol.io.