Secure Muse Code Outlook Connection with PortEden

Prerequisites

• Muse Code (beta) installed and authenticated: curl -fsSL https://dev.meta.ai/install.sh | bash, then muse login. macOS and Linux; on Windows use WSL2.
• A Microsoft 365, Outlook.com, or Exchange Online mailbox you want Muse Code to use.
• If your tenant restricts third-party app consent, an admin who can approve PortEden's Microsoft Graph scopes (see Step 3).

Step 1: Add the PortEden MCP server to settings.json

PortEden's email capability covers Gmail and Microsoft mailboxes through the same hosted MCP endpoint, connected over the streamable_http transport. Nothing to install, nothing to host.

mkdir -p ~/.config/muse 
$EDITOR ~/.config/muse/settings.json 

{ 
  "schema_version": 1, 
  "mcp_servers": { 
    "outlook": { 
      "transport": "streamable_http", 
      "url": "https://mcp.porteden.com/email", 
      "mode": "optional" 
    } 
  } 
} 

Step 2: Sign in to PortEden

The first time Muse Code calls an email tool, the PortEden server requires authentication. This is the single setup screen you will see.

Step 3: Connect Outlook (first-time only)

This step runs only if your PortEden account does not already have a Microsoft mailbox connected. If it does, PortEden reuses the existing connection and you can jump straight to Step 4.

Step 4: Verify the connection

In a Muse Code session, run a low-risk read prompt. Then check the PortEden audit log to confirm the request shows up.

Try one of these

• Muse Code returns real data from your mailbox, not a refusal or an error.
• Sensitive identifiers appear redacted or tokenized if you left redaction enabled.
• The PortEden audit log at my.porteden.com shows the request with a green allow decision.

Step 5: Tighten what Muse Code can do (optional)

The token PortEden created uses conservative defaults: email scope only, redaction on, confirm-before-write for send and delete. Tighten or relax it from my.porteden.com under Access Tokens. Every sub-agent Muse Code spawns uses this same token, so its scope is the boundary for the whole fleet.

Permission presets for a coding agent

Recommended rules for a Muse Code token

• Start read-only: grant write actions only when a workflow proves it needs them.
• Folder exclusions: block HR, Legal, and client-matter folders entirely.
• Contact blocklist: add executive, HR, and personal aliases or whole domains.
• Time window: restrict to the last 90 days unless a workflow needs history.
• Redaction: leave on; what the model never receives cannot be retained or trained on, whatever Meta tier the session runs on.
• Confirm before write: keep on for send and delete.

Suggested prompts for everyday use

Troubleshooting and error handling

Match the message you see to the entries below. For settings-file and connection errors, see also the full troubleshooting table in the Gmail guide, which applies to any PortEden email connection.

Security best practices

FAQ

Next steps