This topic was automatically generated from Slack. You can find the original thread here.
I get this error in development all the time. It seems very inconsistent.
Have you checked out some of the troubleshooting info yet? GitHub
That basically means something is wrong w/ the Connect Token. Either it expired (ctok expiry is 4 hours), or it’s already been used, or the app / oauthAppId are wrong, etc.
Are you getting a Connect Token returned from createConnectToken every time? I guess if you’re creating the token at the time of connectAccount then it could be an issue w/ the createConnectToken call.
the issue was me passing app.id instead of app.slug_name. In the documentation and types, it shows app id to pass but that’s not right.
I have another issue with the frontend sdk. Basically the way it opens iframe, if you already have a modal inside which you put the button, you won’t be able to interact with the iframe.
the issue was me passing app.id instead of app.slug_name. In the documentation and types, it shows app id to pass but that’s not right.
Can you show me where in the docs and the SDK you saw this? I want to make sure we patch if that’s the case
Ah interesting issue w/ the iFrame and auth modal. If that doesn’t work for your app, Connect Link might be a better option?
if I want to use the mcp for my app, should I fork the modelcontextprotocol folder from your github and run it with my config file over private network/proxy for authentication?
npx @pipedream/mcp --help also how does this cli work? like where do I pass the connect environment variables?
does it automatically pick them up from the environment
the repository server also supports streamable-http transport but the cli doesn’t have an option for it
is there an easier way for me to use the mcp endpoint (we are ok with paying for it)? 
The license for MCP server currently do not support commercial use if we were to self host it to use the managed pipedream service.
is there an easier way for me to use the mcp endpoint (we are ok with paying for it)?
Yes we’re very close to releasing a hosted version so you don’t have to host it youself
Is there a fix for this? I cannot get my agent to properly authenticate in development via pipedream and I am seeing the same page. I have tried so many routes to implement this into platform.
I’m sorry to hear you’re having trouble with authentication in Pipedream. Here are a few steps you can try to resolve the issue: 1. Hard Refresh: Try performing a hard refresh of the Pipedream website in your browser. This can help clear any cached data that might be causing issues. 2. Log Out and Log Back In: Sometimes, simply logging out of your Pipedream account and logging back in can resolve authentication issues. 3. Disable Browser Extensions: Browser extensions can sometimes interfere with website functionality. Try disabling your extensions or using a browser mode like Chrome’s Guest mode to see if that resolves the issue. 4. Check Pipedream Documentation: Make sure you’re following the correct authentication steps as outlined in the Pipedream documentation. You can find more information on connecting accounts at Pipedream Connect. 5. Report a Bug: If none of the above steps work, you might be encountering a bug. You can report it by following the instructions in the Pipedream Troubleshooting Guide. If you’re still having trouble, I recommend reaching out to Pipedream support for further assistance. You can visit Support - Pipedream for more support options.
is there a fix for what? What issue are you running into?
I was getting the same session expired when my agent went to authenticate. It seems as if it is struggling to select an app (SELECT_APP). I wanted to ask you if the pipedream AI agent builder is more reliable and then I could move it to my platform after I know it works and wanted to know if that is possible to do. I don’t see any docs on the builder.
Let’s move this to another thread. I’m a bit confused on what you’re trying to do and what issue you’re running into.