Clerk
Clerk developer docs: list and fetch SDK code snippets by tag or by slug.
Tools
Tools discovered when you connect
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
Tools load when your organization connects this server
Clerk can expose tools based on its deployed version and credentials. Runlayer discovers the available list when your organization connects the server.
Compatibility
Connect Clerk to the clients your teams already use
27 AI clients can connect to Clerk through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Clerk through Runlayer?
One approved path
Approve Clerk once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.