PipedreamHQ / PipedreamHQ/pipedream
Lever
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
### App
Lever
### Summary:
The "Connect account" flow for the Lever app fails with an access_denied OAuth error. The flow redirects to Lever's sandbox environment (sandbox-lever.auth0.com) rather than production, which prevents authentication with our production Lever credentials.
### Details:
I'm trying to connect my organization's production Lever instance to Pipedream so I can use Pipedream's MCP server with claude.ai. When I click "Connect account" on https://mcp.pipedream.com/app/lever, the flow opens the Pipedream Connect modal, then redirects to sandbox-lever.auth0.com, then fails and redirects to pipedream.com/popup/auth/error/connect-error?error=access_denied. The "Connection failed. Please retry or contact support." error appears.
Our Lever instance is production (hire.lever.co), not sandbox. I can sign into Lever directly without issue. The OAuth redirect to a sandbox Auth0 tenant appears to be the source of the failure — production credentials cannot authenticate against the sandbox environment.
I also notice the validate endpoint response includes "base_proxy_target_url":"https://api.sandbox.lever.co" and the MCP catalog shows no tools available for the Lever app ("We don't have any tools available for this app yet").
Questions:
Is the Lever connector configured to support production Lever tenants, or is it currently sandbox-only?
If production is supported, what is the correct way to connect a production Lever account?
Are MCP tools planned for this connector, or is it currently a placeholder?
### Screenshots:
Contributor guide
Assessment
This issue has not been assessed yet.