ChatGPT Developer Mode: Full MCP client access
221–230 of 290 posts
Re: ChatGPT Developer Mode: Full MCP client access
#222AI companies: Agentic AI has been weaponized. AI models are now being used to perform sophisticated cyberattacks, not just advise on how to carry them out. We need regulation to mitigate these risks. The same AI companies: here's a way to give AI full executable access to your personal data, enjoy!
what are you saying, this has an early internet vibe! time to explore. isn't this HACKER news? get hacking. ffs
Re: ChatGPT Developer Mode: Full MCP client access
#223Re: ChatGPT Developer Mode: Full MCP client access
#224I tried to connect our MCP ( https://technicalseomcp.com ) but got an error. I don't see any debugging features yet but I found an example implementation in the docs: https://platform.openai.com/docs/mcp
What is the error you are getting? I get "Error fetching OAuth configuration" with an MCP server that I can connect to via Claude.
Something went wrong with setting up the connection
In the devtools, the request that failed was to `https://chatgpt.com/backend-api/aip/connectors/links/oauth/c...` which send this reply: Token exchange failed: 401, message='Unauthorized', url=URL('https://api.mapbox.com/oauth/access_token')Re: ChatGPT Developer Mode: Full MCP client access
#225Earlier quoted context omitted.
Oh man, if you want to see a thinking model lose its mind... write a list of ten items and ask "what is the best of these nine items?"[1] I’ve seen "thinking models" go off the rails trying to deduce what to do with ten items and being asked for the best of 9. [1]: the reality of the situation is subtle internal inconsistencies in the prompt can really confuse it. It is an entertaining bug in AI pipelines, but it can…
Can you elaborate on what it means for a model to "lose its mind"? I tried what you suggested and the response seemed reasonable-ish, for an unreasonable question.
Re: ChatGPT Developer Mode: Full MCP client access
#226Earlier quoted context omitted.
Your question is a bit like asking how a word processor is better than a typewriter... they both produce typed text, but otherwise not comparable.
Interesting, have you used both? A typewriter types when the key is pressed, a word processor sends an interrupt though the keyboard into the interrupt device through a bus and from there its 57 different steps until it shows up on the screen. They’re about as similar as oil and water.
Re: ChatGPT Developer Mode: Full MCP client access
#227Earlier quoted context omitted.
They weren’t kidding about hooking mcp servers to internal databases. You see people all the time connecting LLMs to production servers and losing everything — on reddit. Its honestly a bit terrifying.
Claude has a habit of running ‘npm prisma reset —force’, then being super apologetic when I tell it that clears my dev database.
Re: ChatGPT Developer Mode: Full MCP client access
#228> Eligibility: Available in beta to Pro and Plus accounts on the web. But not Team?
Re: ChatGPT Developer Mode: Full MCP client access
#229Wow this is dangerous. I wonder how many people are going to turn this on without understanding the full scope of the risks it opens them up to. It comes with plenty of warnings, but we all know how much attention people pay to those. I'm confident that the majority of people messing around with things like MCP still don't fully understand how prompt injection attacks work and why they are such a significant threat.
Obviously in some companies employees will look to use it without permission. Why deliberately opening up attackable routes to your infrastructure, data and code bases isn't setting off huge red flashing lights for people is puzzling.
Guess it might kill the AI buzz.
Re: ChatGPT Developer Mode: Full MCP client access
#230Wow this is dangerous. I wonder how many people are going to turn this on without understanding the full scope of the risks it opens them up to. It comes with plenty of warnings, but we all know how much attention people pay to those. I'm confident that the majority of people messing around with things like MCP still don't fully understand how prompt injection attacks work and why they are such a significant threat.
How any mature company can allow this to be enabled for their employees to use is beyond me. I assume commercial customers at scale will be able to disable this? Obviously in some companies employees will look to use it without permission. Why deliberately opening up attackable routes to your infrastructure, data and code bases isn't setting off huge red flashing lights for people is puzzling. Guess it might kill the…
I'm quite surprised it hasn't happened yet.