Other Clients

Any MCP-compatible client can connect to the Parcel server. The approach depends on whether the client supports remote (HTTP) MCP servers or only local (stdio) servers.

Clients with native remote/HTTP MCP support

Point the client directly at the connect URL:

https://mcp.parcelengineering.com/mcp

Consult your client’s documentation for where to add the URL. After adding it, authenticate via the OAuth login when prompted: sign in with Microsoft or Google, or enter your work email and the 6-digit code, then pick a workspace.

Clients that only support stdio (local) servers

Use the mcp-remote adapter as a bridge. Run it as the MCP server command:

Generic stdio bridge

npx -y mcp-remote https://mcp.parcelengineering.com/mcp

Configure your client to launch this command as a local MCP server. The adapter handles the HTTP connection and OAuth flow transparently. The first run opens the Parcel OAuth login in your browser.

Verify it works

Ask your assistant to run search_projects. If it returns project data, the connection is working. The full list of tools is on the Available Tools page.

Note

The first tool call triggers the OAuth login (Microsoft, Google, or email with a 6-digit code, then workspace selection). Subsequent calls use the stored token.