No, Xerox PARC invented the IDE, just like they did with the GUI.

https://en.wikipedia.org/wiki/Xerox_Star

https://en.wikipedia.org/wiki/Xerox_Development_Environment

IDEs go back to how Mesa (Tajo), Interlisp-D and Smalltalk work.

Here are some overview papers

"The Mesa programming environment"

https://dl.acm.org/doi/10.1145/800225.806843

Interlisp-D, you can see all on the recovery project

https://interlisp.org/

And naturally the famous Smalltalk issue on Byte,

https://archive.org/details/byte-magazine-1981-08

Turbo Pascal naturally did what was possible on home computers hardware, the iconic 3.0 version that made it take off was released in 1985.

Long before the term IDE was coined, there were source code editors from within which you could run the shell commands required to build a software project and you could examine their output, e.g. the error messages.

Moreover, interpreters that offered a complete interactive environment for editing, running and debugging programs, had existed for decades for languages like APL and LISP.

Nonetheless, the availability of Turbo Pascal on cheap computers has probably introduced much more people to such a programming environment than the older alternatives, which were available only on big and expensive computers, so at most they were accessible through time-sharing services in big companies or in universities.

I have used Turbo Pascal on 8080- and Z80-based computers running the CP/M operating system, before becoming able to use IBM PC compatibles, where the Microsoft and Borland C and C++ compilers were a better alternative, and it was a good progress over what I had used previously, but before that, in the university I had used a "Remote Job Entry" system which accessed by time-sharing a computer mainframe from a serial video terminal, and you could do with it everything that you could do with Turbo Pascal (for programs written in Fortran), except that its source code editor was far more awkward (it was a line-oriented text editor, where you could see the source code, but to edit a line it was extracted into a buffer at the bottom of the screen and merged back into the source code when editing it was complete).

On CP/M, Turbo Pascal was the most convenient programming environment, but for serious work, where run-time performance mattered, I was using the Microsoft Fortran compiler for CP/M, enhanced by replacing a few of the subroutines from its run-time library with optimized variants. Pascal is really much too weak for number-crunching problems, even if it may be acceptable for non-numeric problems that are not too complex (the original Pascal does not support multi-file programs, Turbo Pascal was extended in a non-standard way to support this).

The Turbo Pascal programming environment was based on UCSD Pascal.