Other Agent Platforms

Handler works with any agent that supports MCP (Model Context Protocol). Here's how to connect the most popular platforms.

Compatibility Table

Platform	MCP Support	Transport	Auth	Status
Windsurf	Full	httpStream	Bearer token	Ready
Cline	Full	httpStream	Bearer token	Ready
Continue.dev	Full	httpStream	Bearer token	Ready
Aider	Partial	stdio	Bearer token	Needs local proxy
Poke	Full	httpStream	API key	Ready
VS Code Copilot	Full	stdio	Bearer token	Needs local proxy
Zed	Full	httpStream	Bearer token	Ready
Roo Code	Full	httpStream	Bearer token	Ready

Windsurf

Add Handler to your Windsurf MCP settings. Open the MCP configuration (Settings → MCP Servers) and add:

{
  "mcpServers": {
    "handler": {
      "url": "https://mcp.usehandler.dev/mcp",
      "headers": {
        "Authorization": "Bearer sk-hndlr-YOUR_KEY"
      }
    }
  }
}

Cline

Cline supports MCP servers natively. Add Handler in your Cline MCP configuration:

{
  "mcpServers": {
    "handler": {
      "url": "https://mcp.usehandler.dev/mcp",
      "headers": {
        "Authorization": "Bearer sk-hndlr-YOUR_KEY"
      }
    }
  }
}

Continue.dev

Add Handler to your Continue configuration file (~/.continue/config.json or the project-level config):

{
  "mcpServers": {
    "handler": {
      "url": "https://mcp.usehandler.dev/mcp",
      "headers": {
        "Authorization": "Bearer sk-hndlr-YOUR_KEY"
      }
    }
  }
}

Poke

Poke is a personal assistant platform with native MCP support. To connect Handler:

Go to Settings → Integrations → Add Custom MCP Server
Set the URL to https://mcp.usehandler.dev/mcp
Add your sk-hndlr key in the authentication field

Poke will automatically discover Handler's tools and make them available in your assistant conversations.

VS Code Copilot

GitHub Copilot in VS Code supports MCP via the stdio transport. Since Handler uses httpStream, you'll need a local MCP proxy to bridge the two transports.

Coming soon. We're working on a stdio transport option for Handler that will allow direct Copilot integration without a proxy. In the meantime, you can use a tool like mcp-proxy to bridge httpStream to stdio.

Generic Setup

For any MCP-compatible agent platform not listed above, you need two things:

Setting	Value
MCP Server URL	`https://mcp.usehandler.dev/mcp`
Transport	Streamable HTTP (httpStream)
Authentication (Option A)	OAuth — the platform handles the flow automatically
Authentication (Option B)	`Authorization: Bearer sk-hndlr-YOUR_KEY` header

If your platform supports httpStream transport and can set custom headers, it will work with Handler out of the box. If it only supports stdio, you'll need a local proxy until we add stdio transport support.

Known Limitations

Stdio-only clients need a local proxy. Platforms like Aider and VS Code Copilot that only support stdio transport cannot connect directly to Handler's httpStream endpoint. A local proxy bridges the gap.
Azure AI Foundry bearer token schema is unsupported. Azure uses a non-standard bearer token format that is not compatible with Handler's authentication.
We're working on a stdio transport option for maximum compatibility. This will allow any MCP client to connect directly, regardless of transport support.

Tip: If your agent platform isn't listed here, check whether it supports MCP. If it does, the generic setup above should work. If not, you can use Handler's REST API instead of MCP.