Connect your AI to your tasks

API key flow

1. Open Settings → Integrations.
2. Click Generate API key. Pick a name, scopes (defaults to all), and expiry.
3. Copy the key now— Maestro stores only a hash; you won't see it again.
4. Paste the snippet below into your client's MCP config and restart it.

Claude Code

Add to ~/.claude/claude_desktop_config.json:

{
  "mcpServers": {
    "maestro": {
      "url": "https://mcp-maestro.tedigo.com/mcp",
      "headers": {
        "Authorization": "Bearer mk_live_…"
      }
    }
  }
}

Codex CLI

Set MAESTRO_API_KEY + point at the hosted endpoint:

# ~/.config/codex/mcp.toml (or your client's equivalent)
[mcp_servers.maestro]
url = "https://mcp-maestro.tedigo.com/mcp"
headers = { Authorization = "Bearer mk_live_…" }

Lost a key, or worried it leaked? Revoke it from Settings → Integrations — any client using it loses access immediately.

OAuth flow (no keys to paste)

1. In your MCP client, add a new server with this URL:

   https://mcp-maestro.tedigo.com

2. Your client opens a browser tab to Maestro's consent screen.
3. Sign in with your usual passkey, Google, or password.
4. Pick which scopes the client can access (read tasks, write tasks, etc.). Click Allow.
5. You're redirected back to the client. Tools work immediately.

Tokens expire every 15 minutes and refresh silently for 30 days. After that you'll see the consent screen again.

Want to disconnect a client? Revoke its tokens from Settings → Integrations.

What your AI can do

The current tool surface mirrors the Maestro web app. A scoped key can be limited to read-only or any subset.