Settings & Billing
Profile, language, plan and limits, API keys, and MCP connection
All your account settings live on the Profile page: https://app.connfig.com/profile. From there you manage your profile details, language, plan, API keys, MCP connection, and sending domains.
Profile and account
- Profile editor: update your display name and avatar.
- Account card: the email you sign in with; set a password or send a password reset email.
- Language selector: switches the application language between Turkish and English.
Plan and limits
The Plan card shows your current plan, maximum workspaces, data (place) limit, seat count, and the next renewal date. The View Plans button leads to the pricing page; on a paid plan you can cancel your subscription here (cancellation takes effect at the end of the billing period).
Free plan limits:
| Limit | Free plan |
|---|---|
| Workspaces | 1 |
| Seats | 1 |
| Places | 25/month |
| Manual CRM records | 25 |
| Campaign emails | None (test emails remain available with their own rate limit) |
Limits on paid plans vary by plan; see the pricing page for current values. The "Lead Generation" card shows the total number of leads you have generated to date.
API keys
API keys are used to connect AI clients such as Claude to the Connfig MCP server (mcp.connfig.com):
- On the API Keys card, click Create Key and enter a descriptive name (e.g. "Claude Desktop").
- The key is generated with the
cnfg_prefix and is shown only once, at creation time — copy it immediately and store it somewhere safe. - The list shows each key's name, prefix, last used date, and creation date. Revoke unused keys with Revoke to invalidate them permanently (cannot be undone).
MCP connection
The MCP Connection Guide card shows how to use Connfig's lead scraping, CRM, campaign, and report features from AI assistants. Your plan limits apply through MCP exactly as they do in the app.
- claude.ai (web) — recommended, no API key needed: follow Settings, Connectors, Add custom connector; enter
https://mcp.connfig.com/mcpas the URL, leave the OAuth Client ID/Secret fields empty, and sign in on the Connfig screen that opens. - Claude Code (terminal): create an API key first, then:
claude mcp add --transport http connfig https://mcp.connfig.com/mcp \
--header "Authorization: Bearer cnfg_YOUR_API_KEY"- Clients using mcp.json:
{
"mcpServers": {
"connfig": {
"type": "http",
"url": "https://mcp.connfig.com/mcp",
"headers": { "Authorization": "Bearer cnfg_YOUR_API_KEY" }
}
}
}Sending domains
Adding and verifying domains also happens on the Profile page; see Sending Domains for details.
Mini scenarios
Scenario 1 — Connecting Claude to Connfig: A marketer wants to query CRM records through Claude. On claude.ai they add a custom connector under Settings, Connectors, enter https://mcp.connfig.com/mcp as the URL, and sign in with their Connfig account. They can now ask Claude things like "list the 10 most recently added leads" directly — no API key required.
Scenario 2 — Upgrading as the team grows: A user on the Free plan wants to invite a second teammate, but the Free plan includes 1 seat. From the Plan card on the Profile page they click View Plans to reach the pricing page and choose a suitable plan; after upgrading, the seat and workspace limits update on the Plan card.