Can Sidekick use tools from a custom MCP server?
Yes. When you register a custom Model Context Protocol (MCP) server, Sidekick calls tools/list on the server URL and treats the tools it finds like any native connector, such as Linear or Datadog.
Calls go through a trusted proxy and are brokered server-side, so your credentials never enter the Sidekick sandbox.
Authentication
- OAuth: Plain brokers the OAuth flow. Users authorize once and Sidekick reuses the token.
- API key: You provide the key name, value and placement, header or query parameter. The key is vaulted and injected at call time.
Things to know
- Workspace-wide scope: Connections are shared by all users in the workspace. There is no per-user authentication. Everyone calls the server with the same credentials.
- HTTPS required: Your server must be reachable over HTTPS at a public URL. Servers on a private network need a public tunnel such as ngrok or Cloudflare Tunnel.
- Tool list is cached: Sidekick snapshots the tool list when you connect. If your server's tools change, reconnect it in Sidekick, under Integrations.
- Limit: Up to 10 custom MCP servers per workspace.
Internal MCP gateway
You can route Sidekick through an internal MCP gateway for tools such as Slack, Git or Grafana instead of connecting to each directly. The gateway controls authentication, access scoping and rate limiting, and Sidekick gets exactly the access it grants.