Clerk MCP server vs Scalekit AgentKit

Clerk MCP server 63

14 tools, two of them for sending feedback to Clerk (15). list_users takes filters; no paging documented (10 of 20). The FAQ explains permission errors and how to fix them (8 of 20). 'Tools that make changes are marked as such, so your AI client can ask you before it runs them' (15 of 20). Official SDKs in many languages and a CLI (15). 15 + 10 + 8 + 15 + 15 = 63.

Scalekit AgentKit 88

Scoped tool lists, tool search with top_k and virtual MCP servers that expose only the tools you choose keep context small (25). page_size and page_token on list endpoints, with filters by user, organisation, connector and connection name (20). Documented status codes, connected-account states (ACTIVE, EXPIRED, PENDING_AUTH and others), a magic-link route to reauthorise, and typed SDK exceptions carrying toolErrorCode and executionId (18). No idempotency keys. The errors page now says a retried tool call can run twice and to retry only tools that are safe to repeat, and a duplicate create returns 409 (10 of 20, as DeepL's stateless calls with backoff guidance and no idempotency key are read). Official Node and Python SDKs and few required fields (15).

Clerk MCP server 65

Typed JSON Schema by protocol, not read because every tool needs sign-in (15 of 25). llms.txt and a .md copy of every docs page (10). The docs table says what each of the 14 tools is for (12 of 20). Input typing not verifiable without a session (5 of 15). Example prompts and an FAQ on permission errors (8 of 15). Dated public changelog with an MCP entry on 15 October 2026 (15). 15 + 10 + 12 + 5 + 8 + 15 = 65.

Scalekit AgentKit 87

OpenAPI 3.1.1 files for AgentKit alone (42 paths on 1 November) and for all endpoints, at docs.scalekit.com/api/agentkit.scalar.json (25). llms.txt with full and small variants, and a Markdown twin for each page (10). Connector pages and the API reference say what each endpoint and connector type is for (15). Filters are typed and constraints stated, for example a search query of at least 3 characters, top_k up to 50 and MCP session tokens from 60 seconds to 24 hours (13). Status codes 400, 401, 403, 404, 409 and 500 are documented, but many response examples are null placeholders (9). Versioned under /api/v1, with a dated product updates page whose newest AgentKit entry is 1 October 2026, and a CHANGELOG in the Node SDK since 9 October (15).

Clerk MCP server 57

Closed service under terms naming Clerk, Inc., last updated 1 October 2026 (15). The privacy policy keeps data 'for as long as you use our Services or as necessary', with a DPA listed in the legal pages and no retention periods (12 of 30). No deprecation policy for the MCP server found (5 of 20). Subprocessors referenced through the DPA, list not read (8 of 20). 15 + 12 + 5 + 8 = 40.

Scalekit AgentKit 66

Closed platform under terms that name ScaleKit, Inc. and Delaware law (effective 1 January 2026), with MIT SDKs (15). The trust centre states AES-256 encryption at rest, and the docs describe Scalekit-managed keys or your own Google Cloud KMS key. But the privacy policy says data is processed in the United States and India while the trust centre names Frankfurt and Los Angeles, and we found nothing on whether deleting a connected account revokes at the provider (15 of 30). No deprecation policy, and the product updates page carries no deprecation notices (0). Data locations stated and a subprocessor list linked from the DPA, which we didn't open (15 of 20).

Clerk MCP server 65

Graded as a hosted service. incident.io status page at status.clerk.com with components for authentication, sessions, webhooks and SCIM, but none for the MCP server (15). The feed shows several resolved incidents since August (an upstream SMS issue on 29 October, Apple sign-in for development instances, an incident across all components on 3 November, resolved), none read as a long core outage (20). Backend API limits published with numbers (1,000 requests per 10 seconds in production), not for the MCP server itself (10 of 15). 429 with Retry-After documented, no idempotency guidance for writes (10 of 15). No SLA found; Business support has 'No response-time SLA' (0). The MCP server isn't labelled beta (10). 15 + 20 + 10 + 10 + 0 + 10 = 65.

Scalekit AgentKit 72

The status page is scalekit.statuspage.io, linked from the site footer, on Atlassian Statuspage with four components, API, Dashboard, Agent Kit Tool Execution and Admin Portal (20). The history page was readable on 1 November. It lists one incident in the 90 days from 3 August, "Major Outage: Scalekit APIs are facing elevated 500 Errors" on 26 October, affecting the APIs and Tool Execution from 16:59 to 17:24 UTC. Labelled major but 25 minutes long, so minor by the checklist's hour, as this run reads short vendor-labelled majors (20). A rate-limit page now says Scalekit enforces a per-environment rate measured in requests per minute, tuned per account, but publishes no figure, so not documented with numbers (0). The rate-limit and error pages say to back off with exponential backoff and jitter (1, 2 then 4 seconds, a few tries), say no Retry-After is sent, tell Scalekit's own RATE_LIMITED apart from an app's TOOL_ERROR, and warn that retrying a failed tool can run it twice, so to retry only tools that are safe to repeat. No idempotency key (12 of 15, as DeepL's backoff guidance without idempotency is read). Enterprise lists a 99.99 per cent uptime SLA on the pricing page (10). No beta labels on the AgentKit endpoints (10). 20+20+0+12+10+10 = 72.