This topic was automatically generated from Slack. You can find the original thread here.
Subject: Request for User API Key (pd_** format) for MCP V2 Endpoint Access
Hello Pipedream Support Team,
I’m reaching out because I’m unable to authenticate with the Pipedream MCP V2 endpoint (https://mcp.pipedream.net/v2) using my current API key format.
What I’m Trying to Do:
I’m building a custom MCP (Model Context Protocol) server called forge-hub that connects to Pipedream’s V2 MCP endpoint to access tools from various Pipedream apps (Google Calendar, Slack, Google Docs, etc.). The server uses Server-Sent Events (SSE) transport and authenticates via Bearer token in the Authorization header.
The Problem:
I’m receiving 401 Unauthorized errors when attempting to connect to the V2 endpoint. The error message is: “SSE error: Non-200 status code (401)”.
API Key Formats I’ve Tried:
- Account API Key starting with
06c(e.g.,06c6....) - This works with the legacy Pipedream endpoints but not V2 - Another API key format (e.g.,
8be....) - Also rejected with 401
What I Need:
Based on Pipedream’s documentation and the V2 endpoint requirements, I need a User API Key that starts with the pd_ prefix. However, when I attempt to regenerate my API key in the Pipedream settings (Pipedream - Connect APIs, AI, databases and more), I’m only receiving numeric keys that don’t start with pd_.
Technical Details:
- Endpoint:
https://mcp.pipedream.net/v2 - Transport: Server-Sent Events (SSE)
- Authentication: Bearer token in
Authorizationheader:Bearer ${API_KEY} - Error: 401 Unauthorized
- Expected Format: User API Key starting with
pd_**
Questions:
- Is my account on a legacy API key format that needs to be migrated to the new
pd_**format? - If so, can you help migrate my account to support the new User API Key format?
- Is there a different section in the settings where I should generate a User API Key specifically for MCP/Connect API access?
- Are there any account-level requirements or permissions needed to access the V2 MCP endpoint?
Additional Context:
I’ve successfully used the legacy Pipedream endpoints ([remote.mcp.pipedream.net/default/{appSlug}](http://remote.mcp.pipedream.net/default/{appSlug})) with my Account API Key, but I’m migrating to the unified V2 endpoint for better OAuth handling and tool management. The V2 endpoint appears to require the new pd_** format specifically.
I’ve also reviewed the Pipedream documentation which indicates that Personal Access Tokens (User API Keys) should follow the pd_ prefix format as of 2026, but I’m unable to generate one through the UI.
Thank you for your assistance. Please let me know if you need any additional information or logs to help resolve this issue.
Thanks
