One address, one sign-in, your role | DATASPHERES AI - Dataspheres AI

AI assistants reach outside tools through the Model Context Protocol, usually shortened to MCP. It is an open standard, and it is the same one Claude, Curs...

AI assistants reach outside tools through the Model Context Protocol, usually shortened to MCP. It is an open standard, and it is the same one Claude, Cursor, VS Code, GitHub Copilot and OpenAI Codex all use, which is why a single server can serve all of them. Dataspheres AI runs such a server at https://dataspheres.ai/mcp . That address is the only thing any assistant needs to know. The first time an assistant uses the address, it opens a Dataspheres sign-in window in your browser. You sign in with the account you already use in the app and approve the access. From then on the assistant holds a token that identifies you, and the token expires on its own after a while, at which point the assistant simply asks you to sign in again. No API key is copied anywhere, and nothing runs on your computer beyond the assistant itself. The part that matters most for a non-technical user is how access works. The connection is scoped to your account, and your role in each datasphere (participant, moderator, owner and so on) is checked live on every call. If you can edit a page in the app, the assistant can edit it for you. If you cannot, the assistant receives a refusal that names the role it would need. There is no separate set of permissions to manage, and an assistant can never do more than you could do yourself. In short The address is https://dataspheres.ai/mcp and it is the same for every assistant. You sign in once with your Dataspheres account; the assistant keeps a token that expires on its own. Your role in each datasphere applies, checked live, on every action.