favcrm/mcp / skills/favcrm-agentic-registration
favcrm-agentic-registration
UnverifiedUse when a new user wants to register for FavCRM from inside an MCP client, create a FavCRM workspace, request or verify signup OTP, receive a fav_mcp_* API key, or continue setup after agentic registration.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 8 B |
| SKILL.md | skill md | 2.0 KB |
| agents/openai.yaml | config | 190 B |
| references/agentic-registration-flow.md | markdown | 1.3 KB |
references/agentic-registration-flow.md
View on GitHub# Agentic Registration Flow
## Step 1: Request Code
Call:
```json
{
"name": "register_organisation_request",
"arguments": {
"organisationName": "Stretch + Breathe",
"email": "owner@example.com",
"industry": "fitness",
"country": "HK",
"timezone": "Asia/Hong_Kong"
}
}
```
Expected result includes:
- `requestId`
- `expiresAt`
- `maskedEmail`
- `instructions`
Tell the user to check the masked inbox and paste the 6-digit code.
## Step 2: Verify Code
Call:
```json
{
"name": "register_organisation_verify",
"arguments": {
"requestId": "<requestId from step 1>",
"code": "123456"
}
}
```
Expected result includes:
- `organisationId`
- `companyId`
- `userId`
- `apiKey`
- `loginUrl`
- `nextSteps`
## Key Handling
Tell the user:
- Use `Authorization: Bearer <apiKey>` for future MCP calls.
- Store the key in an environment variable such as `FAVCRM_API_KEY`.
- Do not commit the key to source control.
- Use `loginUrl` and forgot-password flow to set a portal password.
## Failure Handling
- Existing email: user should sign in at `https://app.favcrm.io` and create an MCP key from settings.
- Expired code: call `register_organisation_request` again.
- Wrong code: ask the user to re-check the email code.
- Rate limit: report the tool summary and wait; do not loop retries.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |