Death to clickops ☠️
With Clerk’s MCP server, your agent can create an app, configure auth, and set up a production instance with DNS records and next steps to go live.
clerk.com/blog/clerk-mcp-ser…
1. Use your coding agent to setup MCP auth
Setting up MCP auth shouldn’t require fiddling with a dashboard or a degree in identity specs.
Just install Clerk's plugin, then ask your agent to set up auth for your MCP server. The plugin will help your agent set up auth properly, including serving important /.well-known artifacts for discoverability.
Install our plugin: npx plugins add clerk/skills
If @bot needs data from Clerk that our plugin doesn't support yet, reply with what you need and our team will add a tool for it.
3. Miscellaneous AX improvements
- Our 404 now returns markdown to agents
- Our MCP server card has been republished in conformance with the standard
- Our llms.txt is now discoverable from our homepage
- Our MCP handshake now shares a title, description, icon, and instructions
- We're now returning a Poppy manifest, and plan to support Poppy-based agent auth very soon
Use agents to build and maintain your application with Clerk:
"List the five most recent sign-ups."
"Create a test user in the development instance."
"Set the DNS records for production."
Long overdue ship: actually useful @clerk MCP server tools! Give it a whirl. Let us know what you like and what sucks... and direct through X/twitter, or better yet, get your agents to yell at us via the feedback tool. 🤖 🤝 🍪
clerk.com/changelog/2026-10-…




