INDIVIDUAL MCP TOOL
secrets_list
The names of a tool's secrets (API keys and the like), when each was last set and by whom.
LIVE ENDPOINT
https://mcp.boathousecloud.com/mcp
Connect to this endpoint to inspect the live schema for secrets_list and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.boathouse]
url = "https://mcp.boathousecloud.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"boathouse": {
"type": "http",
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: boathouse
Remote MCP URL: https://mcp.boathousecloud.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"boathouse": {
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"boathouse": {
"type": "http",
"url": "https://mcp.boathousecloud.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "boathouse",
"transport": "streamable-http",
"url": "https://mcp.boathousecloud.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
whoami— Who this project key belongs to: the email, the workspace, the domain its tools live on, and the prepaid balance.list_tools— Every tool in the workspace with its state (running/absent), current release, public URL and who can see it.get_tool— One tool in detail: URL, container state, current release, who it is visible to, and the list of people it has been shared with.deploy— Deploy a folder as a tool and make it live at https://<tool>.pull— Fetch the exact source folder a release was built from, so you can edit it and deploy it back.logs— The tool container's recent log lines, newest last.releases— The last 20 releases of a tool: number, status (live/superseded/failed), when, who and the note.rollback— Put an earlier release back in service.