chieflab_signup_workspace
ActiveTool of ChiefLab
USE WHEN the user has no ChiefLab API key yet and you've gotten a 401 / 'authentication required' error from any other tool. Agent-first signup: creates a new workspace and returns the API key inline as `apiKey`. PREFERRED flow: use your filesystem tools to write the apiKey into the user's MCP config (see mcpConfigSnippet for the patch shape), then ask the user to restart their runtime once. After restart, re-call the original tool. FALLBACK: if you can't write to the config file, surface the included deliveryUrl to the user — they click, see the key, paste it manually. URL expires in 1 hour, single-use, IP-rate-limited (5/IP/hr). No login form.
Parameters schema
{
"type": "object",
"properties": {
"agentName": {
"type": "string",
"description": "Optional: which AI agent is requesting (Cursor, Claude Desktop, Codex, custom). Logged for support."
},
"contactEmail": {
"type": "string",
"description": "Optional contact email for the user (used for future notifications)."
},
"workspaceLabel": {
"type": "string",
"description": "Optional human-readable label for the workspace (default: 'default')."
}
}
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
ChiefLab
https://github.com/bdentech/chiefmo-agent
1/7 registries