Connect PortEden to Muse Code

Prerequisites

• Muse Code installed and authenticated (curl -fsSL https://dev.meta.ai/install.sh | bash, then muse login). Muse Code runs on macOS and Linux; Windows requires WSL2.
• A PortEden account, sign up or sign in at my.porteden.com
• At least one service connected inside PortEden (Gmail, Outlook, Google Calendar, Drive, etc.), or connect it during the auth flow

Step 1: Open the Muse Code Settings File

Muse Code reads user settings from ~/.config/muse/settings.json. Create the file if it does not exist. It must declare "schema_version": 1 or Muse Code refuses to start with a malformed settings file error.

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

Step 2: Add a PortEden MCP Server

Add the PortEden endpoint for the capability you want under mcp_servers, using the streamable_http transport. For example, email:

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

Restart Muse Code. On the first tool call the server requires authentication: complete the PortEden sign-in when it opens (sign up in the same flow if you have no account). PortEden then issues a scoped access token for this connection, and you never paste raw Google or Microsoft credentials anywhere.

Step 3: Add More Connections

Each PortEden capability is its own MCP server with its own endpoint and its own scoped token. Add only the ones your workflows need:

A combined config with several servers:

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

Step 4: Test the Connection

Start a Muse Code session in any repository and try a low-risk read prompt for each connection you added:

If Muse Code responds with data from the connected service, the connection is working. To see the tools it discovered, ask it to "list every tool available from the email server with a one-line description each." Then check the audit trail at my.porteden.com to confirm the calls were logged.

A Note on Sub-Agents

Muse Code fans large jobs out to parallel sub-agents (up to 16) in isolated git worktrees. Worktree isolation protects your working copy; it does not partition data access. Every sub-agent uses the session's MCP connections, so the PortEden token's scope is the effective boundary for the whole fleet. Keep coding-agent tokens read-only by default, and use access rules (contacts, labels, time windows) to shrink what any child can pull into context.

Managing Permissions

The access token Muse Code receives inherits the permissions you configure at my.porteden.com. You can:

• Restrict Muse Code to read-only access (no sending, no deleting)
• Limit access to specific providers or accounts
• Block contacts, domains, or labels from AI access
• Set time windows (e.g., only see emails from the last 30 days)
• Require confirm-before-write on send and delete actions
• Revoke the token at any time, takes effect on the next call

See Permissions and Access Rules for full details.

Troubleshooting

Next Steps