Open the CocoInbox secure login portal (browser). Prefer this over asking for passwords in chat.

When presenting the result:

• Show a short connect card with the login link/button.

• Do NOT write multi-step "copy auth code" instructions.

• If portal_opened is true, the window should already be open.

• If the user later pastes a one-time code, call complete_login({ code }). Clients with MCP OAuth can also use the built-in Authenticate / mcp_auth flow instead.

Alias for login — open the CocoInbox secure connect portal. Preferred name for "log me in" / "get user" when not authenticated.

Finish browser login only when the user pastes the one-time auth code from the success page (fallback if OAuth/portal did not auto-connect).

Fallback programmatic login (prefer login/connect portal or MCP OAuth). Use only if the user explicitly pastes credentials.

Clear the in-memory auth session and selected sender email.

Return the authenticated user profile (includes company when set).

If not connected: opens the secure login portal automatically and returns a login_portal card — present that card, do not invent multi-step paste instructions.

Show whether this MCP process is authenticated. If not, returns a login_portal card (call connect/login or open the URL).

Get the user privacy / security score (GET /api/security/score).

Scan one email address on the dark web for breaches (POST /api/security/dark-web-scan).

Scan the account email plus all ephemeral addresses (POST /api/security/dark-web-scan-all).

List mail dossiers/folders for the user (GET /api/folders).

Create a new mail dossier/folder (POST /api/folders). Example name: "Work" or "mail/aze-walid".

Create a dossier for a mailbox address (default name mail/). Optionally use a custom folder name.

Move a message (inbound or sent) into a dossier (PATCH /api/mail/messages/:id/move).

List ephemeral email addresses for the logged-in user.

Create a new ephemeral CocoInbox address. Optionally auto-select it as From.

Select which mailbox address to send from (id from list_emails, or "fixed").

Fetch the message thread for one mailbox address.

Send an email via POST /api/mail/send using the selected From address. Automatically moves the sent message into the "MCP" dossier.

Save an idea to the user's CocoInbox account (title + description). Same as the Ideas page on the website. Use when the user wants to note a product/feature wish, or when no existing MCP tool covers their need — do not invent fake tools.

List ideas (title + description + status) previously submitted for this authenticated account. Same data as CocoInbox → Ideas (/ideas).

Alias for submit_idea. Prefer submit_idea.

Alias for list_my_ideas. Prefer list_my_ideas.

Compact CRM counts for this user (groups, leads, tasks todo). Start here to see state without loading full lists.

Create a lead group (campaign). REQUIRED: name + why (outreach reason, e.g. "car garages without websites in Casablanca → pitch website build"). Also set source_ai (claude|grok|cursor|manual) and optional location. Returns group id for crm_add_leads.

List CRM lead groups (token-friendly table). Filter: status active|paused|archived.

When presenting the result:

• Display as a Markdown table using content.columns / content.rows.

• Do not output raw JSON unless the user asks.

• For empty results, show content.empty.

• Keep why short; full why is in crm_get_group.

Get one lead group by id (includes why / source_ai / location).

Add up to 25 leads to a group you own. Include name, email, phone, company, address, city, map_url, website, has_website=false when no site. Private to this user — no cross-user leak.

List CRM leads as a table (optional group_id / with_email / status).

When presenting the result:

• Display as a Markdown table using content.columns / content.rows.

• Do not output raw JSON unless the user asks.

• For empty results, show content.empty.

• Prefer company + name; show "sans site" when has_website is false.

For a group: create email_prospect tasks for leads that have emails. Each task brief + draft uses group.why. Never sends email — returns drafts. After review, send with send_email and mark task done via crm_update_task.

List CRM tasks as a table (optional group_id / status todo|doing|done|cancelled).

When presenting the result:

• Display as a Markdown table using content.columns / content.rows.

• Do not output raw JSON unless the user asks.

• For empty results, show content.empty.

• After sending a prospect email with send_email, mark the task done via crm_update_task.

Update one of your leads (status, email, notes, etc.). Ownership enforced server-side.

Update a CRM task status or draft. After sending prospect email via send_email, set status=done.

Get the user's company profile + generated report (name, what they do, offer, audience).

When presenting:

• Summarize the company clearly (name, what they do, offer).

• If configured=false, tell the user to fill Profil → Entreprise or call update_company_profile.

• Use this before creating CRM groups / prospect tasks so outreach matches the real business.

Save/update the sender company profile. Regenerates an AI report used to refine CRM prospect emails.

Required: name OR description. Prefer filling name, description (what you do), and offer (what you pitch).