Source
Sharing, permissions & administration — found from sitemap — Excalidraw+
Checked for Excalidraw+ on 1 Nov 2026
- Page
- https://plus.excalidraw.com/docs/mcp/auth-and-permissions
- Checked
- 1 Nov 2026, 09:17 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:0f1f622cd2a8d35cb15d8edd9075b4b954c4f9bf4faefee82105d20755044c45
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Mcp auth API key Report an error
“MCP authentication uses the same API key system as the public API.”
-
Mcp bearer auth Report an error
“Send your key as Authorization: Bearer <API_KEY>”
-
Mcp keys workspace scoped Report an error
“Keys are workspace-scoped, so tools only access that workspace data”
-
Mcp permission model Report an error
“MCP does not bypass API permissions. Each MCP tool is mapped to a public API route + method, and tool access is granted only when that route is allowed for the key.”
-
Mcp key permission tiers Report an error
“Read-only keys expose read-only tools”
-
Mcp full access keys Report an error
“Full-access keys expose create/update/delete tools”
-
Mcp route restricted keys Report an error
“Route-restricted keys expose only matching tools”
-
Mcp key management guidance Report an error
“For full key management guidance, see API Authentication.”
Scores citing this record
- The Public-Sector Project Lead Integrations, import & export