Connect PortEden to Claude Desktop
This guide walks you through connecting PortEden to Claude Desktop using the config file. Claude Desktop uses the mcp-remote package to bridge remote MCP servers into its local config format.
Tip
Prerequisites
- A PortEden account at my.porteden.com with at least one service connected
- Claude Desktop installed (download here)
- Node.js installed (required for
npx/mcp-remote)
Step 1: Open the Config File
Claude Desktop stores MCP server configuration in a JSON file. You can open it from Claude Desktop via Settings > Developer > Edit Config, or navigate to it directly:
Windows
%APPDATA%\Claude\claude_desktop_config.jsonmacOS
~/Library/Application Support/Claude/claude_desktop_config.jsonLinux
~/.config/Claude/claude_desktop_config.jsonIf the file doesn't exist yet, create it with an empty JSON object: {}
Step 2: Add PortEden Connections
The config file uses mcp-remote to bridge PortEden's remote endpoints into Claude Desktop's local stdio format. Add the connections you need:
Note
mcp-remote wrapper, which runs a local process that proxies requests to the remote endpoint.Start with email and calendar
{ "mcpServers": { "porteden-email": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/email"] }, "porteden-calendar": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/calendar"] } } } All six connections
{ "mcpServers": { "porteden-email": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/email"] }, "porteden-calendar": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/calendar"] }, "porteden-drive": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/drive"] }, "porteden-google-docs": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/google-docs"] }, "porteden-google-sheets": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/google-sheets"] }, "porteden-tasks": { "command": "npx", "args": ["mcp-remote", "https://mcp.porteden.com/tasks"] } } } | Connection | Endpoint | What It Covers |
|---|---|---|
| https://mcp.porteden.com/email | Gmail and M365 email | |
| Calendar | https://mcp.porteden.com/calendar | Google Calendar and Outlook Calendar |
| Drive | https://mcp.porteden.com/drive | Google Drive files and folders |
| Google Docs | https://mcp.porteden.com/google-docs | Search, read, and edit Docs |
| Google Sheets | https://mcp.porteden.com/google-sheets | Read, write, and append to Sheets |
| Tasks | https://mcp.porteden.com/tasks | Monday, Linear, Asana, Jira, Notion |
Step 3: Restart Claude Desktop & Sign In
Save the config file and restart Claude Desktop completely. On the first request to each connection:
mcp-remote starts a local process that connects to the PortEden endpoint.
A browser window opens with the PortEden OAuth consent screen. Sign in with your PortEden account and approve the connection.
The token is stored locally. Subsequent requests use the cached token until it expires or is revoked.
Step 4: Verify the Connection
Try asking Claude something that uses your connected services:
Troubleshooting
Claude doesn't see the PortEden tools
Make sure the config file is saved with valid JSON and you restarted Claude Desktop. Verify Node.js is installed by running npx --version in a terminal.
"Authentication failed"
The OAuth token may have expired or been revoked. Restart Claude Desktop to re-trigger the sign-in flow.
"Permission denied"
Go to my.porteden.com and check the token's permissions.