Most developer quickstarts still assume the same old flow:

open a signup page

create an account

find the API key screen

copy the key

paste it into your tool

finally make the first call

That is fine for a normal dashboard-first SaaS product.

It is awkward for an agentic backend.

If the whole point is that an AI agent can operate the backend, registration should also be something the agent can help with. The user should be able to say:

Sign me up for FavCRM. The business is a yoga studio called Stretch + Breathe in Hong Kong.

Then the agent should request the signup code, wait for the user to paste it back, verify the code, and receive an API key.

That is what FavCRM's agentic registration flow does.

What we are building

By the end of this article, you will have:

a FavCRM workspace

a verified owner email

a fav_mcp_* API key

a configured CLI

a first diagnostic check against the MCP endpoint

You can run the flow through an MCP client or through the favcrm CLI.

Path A: register from an MCP…