One URL
Setup
None
API key needed
Spectare speaks the Model Context Protocol, and every workspace now has its own dedicated connector endpoint at spectare.ai/api/mcp/{orgSlug}. You paste that URL into ChatGPT under Settings, Apps, and your workspace content brain is connected in seconds.
The reason a per-workspace URL matters is that ChatGPT and most consumer MCP clients configure a connector with a URL alone. There is no mechanism to pass custom headers, which is how the previous header-selected org server worked. That approach was unreachable from exactly the clients your buyers use day to day. The new route fixes that without changing anything for API integrations that do set headers.
Unknown slugs return a 404 rather than falling through silently to Spectare's own server. If a URL works, it is connected to the right workspace. If it does not, you know immediately rather than discovering the problem when a visitor gets the wrong content.
The root MCP endpoint stays byte-identical, so nothing breaks for existing integrations. You gain a second surface without losing the first.
This is one atom from the Spectare content library. Spectare assembles the right atoms for each visitor in real time, based on who they are and how they arrived.