Clerk Authentication
This MCP server implementation provides a bridge between Claude Desktop and Clerk-protected API routes or server actions. Developed by Sokratis Vidros, it allows an AI assistant to impersonate a Clerk user, enabling secure interactions with authenticated endpoints. Built using TypeScript and Cloudflare Workers, the implementation focuses on maintaining user authentication while facilitating AI-driven operations. It's particularly useful for scenarios where AI assistants need to interact with protected resources, such as personalized data retrieval or secure API interactions, within applications that use Clerk for authentication.
Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.
Scan details: Circle-IR · 2026-09-28 · Appeal
View full trust & usage report →Metadata
- Version
- 1.0.0
- Skill type
- atomic
- Execution layer
- mcp-remote
- Category
- cloud-infra
- Source
- PulseMCP
- Repository
- github.com/sokratisvidros/workers-mcp-clerk
- Author type
- human
- Last scanned
- 2026-09-28
- Updated
- 2026-09-28
Use via MCP
Resolve Clerk Authentication from your agent
Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.
One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp--scope user for --scope project to commit it to .mcp.json.