Other MCP clients → Conductor¶
Live hub: https://conductor-konstant.hectorsanchez.eu/connect.md
Bootstrap: https://conductor-konstant.hectorsanchez.eu/connect/bootstrap.md
Offline: docs/guides/connect/others.md
Agents: use absolute URLs above. Relative ../connecting.md links 401 on the live host.
Shared rules:
- Transport: Streamable HTTP MCP at
https://conductor-konstant.hectorsanchez.eu/mcp - Prefer header
Authorization: Bearer …with an env-var reference - Never write a literal token into config
- Restart the client after config/env changes
- Success =
tools/listincludessetuponly (compiler tools archived) - Smoke:
curl -fsS https://conductor-konstant.hectorsanchez.eu/connect/mcp-smoke.sh | bash
OpenClaw¶
openclaw.json:
{
"mcpServers": {
"conductor": {
"url": "https://conductor-konstant.hectorsanchez.eu/mcp",
"headers": {
"Authorization": "Bearer ${CONDUCTOR_MCP_AUTH_TOKEN}"
}
}
}
}
Cline (VS Code)¶
{
"cline.mcpServers": {
"conductor": {
"url": "https://conductor-konstant.hectorsanchez.eu/mcp",
"headers": {
"Authorization": "Bearer ${CONDUCTOR_MCP_AUTH_TOKEN}"
}
}
}
}
Windsurf¶
windsurf.json or .windsurf/mcp.json:
{
"mcpServers": {
"conductor": {
"url": "https://conductor-konstant.hectorsanchez.eu/mcp",
"headers": {
"Authorization": "Bearer ${CONDUCTOR_MCP_AUTH_TOKEN}"
}
}
}
}
Continue.dev¶
{
"mcpServers": [
{
"name": "conductor",
"url": "https://conductor-konstant.hectorsanchez.eu/mcp",
"headers": {
"Authorization": "Bearer ${CONDUCTOR_MCP_AUTH_TOKEN}"
}
}
]
}
Generic / header-less clients (last resort)¶
If the client cannot send custom headers, query auth works but leaks more easily (proxy logs, shell history, referrers):
https://conductor-konstant.hectorsanchez.eu/mcp?key=<use-env-expansion-not-a-pasted-secret>
Prefer fixing the client to send Authorization instead.
Pi¶
Stock Pi has no native MCP. Follow the single connect page
(https://conductor-konstant.hectorsanchez.eu/connect.md): smoke script +
Streamable HTTP setup, or a Pi extension. Do not expect Cursor/OpenCode-style
MCP JSON alone.
Generic harnesses¶
Launch strings for other setup(..., harness=…) values come from the setup
tool response. Prefer /connect.md over this file.