Configure Appearance, Plugins, API Access, and Community MCP

Open Creator console → Settings → Advanced.

Appearance

Choose a curated accent or enter a custom HSL value. Clases reports light/dark contrast and can adjust the value toward AA contrast.

Check buttons, links, focus rings, charts, disabled controls, error states, and high-contrast text in light and dark mode. Color must not be the only status cue.

Plugins

Enable only integrations with a named owner, purpose, approved data flow, and offboarding plan. Membership questions collect access-request context. IFTTT, Make, and Zapier can send or receive governed automation events.

Before enabling a plugin:

1. identify the records it can read or change;
2. test with non-sensitive sample data;
3. document the connection owner and failure alert;
4. verify retry/idempotency behavior;
5. record how to disable and rotate credentials.

API Access and MCP

Create a named, read-only personal access token by default. Enable approved write scopes only when the client needs them. Copy the client configuration once, store the bearer token in credential storage, and test a read before any write.

Tokens inherit the permissions and policy attached to them. Use separate tokens for separate clients, choose an expiry, review the audit log, rotate on personnel or vendor changes, and revoke a retired or exposed connection. Never place a token in Help, a screenshot, a post, source control, browser code, or a support transcript.

See Connect an AI client with Clases MCP for supported clients, scopes, and revocation.

If a connection fails, verify the endpoint, token status, scope, community identifier, and server time. Do not broaden scopes until the specific denied operation is understood.