... specification versions , making it easier to connect MCP clients and servers that are not yet running the latest protocol version. On the authentication side, we improved MCP Auth and Enterprise SSO compatibility for identity providers such as Auth0, Okta, and Keycloak . Our documentation has also been expanded with updated guidance for these authentication and authorization flows. We have also expanded our production infrastructure with additional server capacity to support growing MCP workloads and improve scalability, workload distribution, and platform resilience ...

... flags wasted subscription spend the moment usage data is imported, instead of waiting for someone to open a report. Cross-references what you're paying for against who's actually logging in (via Google Workspace, Microsoft 365, or Okta exports), and surfaces the exact $ recoverable per tool. Also just packaged it as a single Windows .exe no install, no terminal, nothing to configure. Runs entirely on your own server, sold as a one-time license instead of another subscription ...

... quest, and then maintain them forever. My bias is obvious, I do product at an identity platform, of course I would say this. And there are real exceptions. If identity is your core product, build it. If you are Okta, build it (obviously). But for everyone else, the build decision usually comes from engineers underestimating the boring 80%, password resets, email deliverability, account lockouts, the audit log someone asks for eight months in. The fun part, the login form ... ... dependent, some older user bases still reach for a password out of habit. Did you get any complaints when you dropped it, or did nobody miss it? Comment from Adam Foster(@adam_foster5): @roguetink This is a classic build vs

... just launched SCIM provisioning for Basedash. It syncs users and groups from Okta or Entra so IT doesn't have to manually manage access as people join, move teams, or leave. Nobody has ever dreamed of building this. There's no demo video that makes SCIM look cool (trust me, we tried). But it's probably going to close more enterprise revenue than features we spent 10x longer on. So I'm curious what this looks like for other people ...

... upmarket, our answer to most security questionnaire items was "not yet." Today the checklist looks pretty different: SSO (SAML and OIDC) : authenticate through the identity provider your company already uses SCIM provisioning : users, groups, and memberships sync automatically from Okta or Entra as people join, move teams, or leave RBAC : groups with fine-grained permissions on data sources, dashboards, chats, automations, and MCP servers Row-level security : control which rows each person can see, and the AI respects those policies ...

... actually grab them, and the card you re resizing stays cleanly on top with no distracting drop shadow. SCIM provisioning for enterprise teams Basedash now supports SCIM 2.0, so enterprise teams can connect an identity provider like Okta or Microsoft Entra ID and automatically provision, update, and deactivate members and keep groups in sync without managing access by hand. Admins generate a SCIM token from Settings Security, drop the base URL into their IdP, and membership follows whatever their directory ...