Read projects, logs and deployments on a self-hosted Windlass server; deploy, roll back, promote.
Connect Remote server
claude mcp add --transport http windlass https://{host}/api/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"windlass": {
"url": "https://{host}/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"windlass": {
"type": "http",
"url": "https://{host}/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://{host}/api/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer followed by a Windlass API token from Settings, API tokens |
Details
| Endpoint | https://{host}/api/v1/mcp (Streamable HTTP) |
| First published | 11 Nov 2026 |
| Last updated | 11 Nov 2026 |
| Registry name | run.windlass/windlass |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
