Bring any tool to Sidekick#
MCP (Model Context Protocol) servers let you extend Sidekick with custom tools beyond the built-in integrations. Register a server, and Sidekick automatically discovers the tools it exposes.
Open Sidekick > MCP Servers to manage your server registry.
What is an MCP server?#
An MCP server is an HTTP endpoint that implements the Model Context Protocol specification. It advertises a list of tools — each with a name, description, and input schema — that an AI agent can invoke.
Registering a server#
- Open Sidekick > MCP Servers
- Click Add Server
- Provide:
| Field | Description |
|---|---|
| Name | Human-readable label for the server |
| Slug | URL-safe identifier (auto-generated from name) |
| Server URL | The HTTPS endpoint of the MCP server |
| Auth type | How Sidekick authenticates — bearer token, API key, or none |
| Auth token | The credential (encrypted at rest, never shown in full) |
- Toggle Enabled to let Sidekick use the server immediately
Tool discovery#
Once registered and enabled, Sidekick queries the server for its tool manifest. Discovered tools appear in the Tools page, where you can test them and control which ones are available.
Security#
- Auth tokens are encrypted at rest and never displayed after initial entry
- The
hasAuthTokenindicator shows whether a credential is stored - Disabling a server immediately prevents Sidekick from calling its tools
info You can register multiple MCP servers. Tools from all enabled servers are available in a single unified tool list.
warning MCP servers run outside LumenFlow's infrastructure. Vet the server before registering it — Sidekick will call any tool the server advertises, subject to your governance rules.
Next step#
Browse and test individual tools in Tools.