Skip to content

Revise MCP setup guide: update personal access token generation proce… #1983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MikaKerman merged 1 commit into from
Aug 14, 2025
Merged

Revise MCP setup guide: update personal access token generation proce… #1983

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 9 additions & 12 deletions docs/cloud/mcp/setup-guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,18 +29,15 @@ npm install -g mcp-remote@latest
---

## 2 – Generate a personal access token
**Design Partner Stage:** Personal access tokens are currently available to design partners only. To obtain a token, please reach out to the Elementary team and we'll provide you with one manually.
**Coming soon:** Self-service token management will be available directly from the Elementary UI for all users.
Elementary issues **user‑scoped bearer tokens**.
These tokens inherit **your** workspace permissions:
* Treat them like passwords – **do not share or commit** them.
* Rotate regularly.
* Revoke immediately if compromised.

### Security reminders
* Tokens confer **all** your Elementary permissions.
* Keep them secret and scoped; rotate when in doubt.
* Revoke compromised tokens immediately.
You can now generate tokens directly from the Elementary UI: go to [User → Personal Tokens](https://demo.elementary-data.com/settings/tokens).

Quick steps:
1. Open the **User → Personal Tokens** page and click **Generate token**.
2. (Optional) Add a name/description.
3. Copy the token and store it securely — it is shown once. Manage (revoke/rotate) anytime from the same page.

### Security
Tokens are **user‑scoped bearer tokens** and inherit your workspace permissions. Treat them like passwords — do not share or commit them. Keep them secret, rotate regularly, and revoke immediately if compromised.


---
Expand Down
Loading