Setting up a browser profile in Incogniton takes less than a minute when you know the settings you need. But the work adds up when you're onboarding dozens of clients. For an agency managing 50 clients, that could mean creating profiles, naming them, assigning proxies, organising them into groups, and applying the right tags.
A single mistake, such as assigning the wrong proxy or putting a profile in the wrong group, can create problems later.
Bulk profile creation reduces this repetitive work. Instead of configuring every profile individually, you can use a CSV import, Incogniton's built-in AI assistant, an API script, or Claude connected through the Incogniton MCP server to create multiple profiles at once.
The best method depends on your team's technical skills and how much control you need over the setup. This guide compares the options, then walks through how to use Claude and Incogniton MCP to create 50 client profiles in batches, organise them, and assign proxies.
Why Manual Profile Setup Breaks at Scale
Manual setup works well for a handful of accounts. At agency scale, however, three problems become more noticeable.
- It takes time. Naming, grouping, tagging, and assigning proxies to dozens of profiles involves repeating the same steps.
- It creates inconsistencies. Different teammates may use different naming conventions, tags or folder structures, making the profile library harder to manage.
- It increases the risk of mistakes. A profile assigned to the wrong group or an incorrectly configured proxy can disrupt account access and complicate client management.
Automation reduces the repetitive work and makes it easier to apply the same setup rules across every client. It does not eliminate the need for oversight, particularly when assigning proxies or managing access to shared accounts.
Your Options for Bulk Profile Creation in Incogniton
Incogniton offers several ways to create and organise browser profiles in bulk. The right approach depends on whether you prefer a straightforward import, an in-app assistant, a repeatable script or natural-language instructions.
1. Native bulk profile creator
Incogniton supports bulk browser profile creation through CSV import. Each row in the file represents a profile, making this option suitable for agencies that already maintain client onboarding data in spreadsheets.
The process is straightforward:
- Open the dropdown next to New profile.
- Select Import from CSV.
- Upload your CSV file or paste its contents.
- Review the detected headers and profile data.
- Check the preview, remove any unwanted rows and confirm the import.
The profiles appear in your profile list after the import. This approach is useful for onboarding batches of accounts without configuring each one manually.
Its main advantage is simplicity: you can prepare the data in a spreadsheet and import it directly. However, if your workflow involves more complex operations, such as creating client groups, applying tags and assigning proxies according to specific rules, you may need additional steps.
2. Incogniton's built-in Cas assistant
Incogniton's Cas AI assistant lets you describe the setup you want in plain language. It can help create profiles in bulk, create groups and tags, and add proxies.
Because Cas is built into Incogniton, you don't need to configure a separate connection to an external AI tool. It's a practical starting point if you want AI-assisted profile management without setting up an automation environment.
3. Scripts with the Incogniton API
The Incogniton API allows developers to automate profile creation through code. You can build scripts that follow a predefined onboarding process and reuse them whenever new clients come on board.
This approach suits teams that need precise, repeatable workflows or want to integrate profile creation with their existing systems. The trade-off is that someone needs the technical skills to build, test and maintain the scripts. API access is included from the Entrepreneur plan upward.
4. Claude with the Incogniton MCP server
The Incogniton MCP server connects Claude to Incogniton so you can manage profiles using natural-language instructions.
You can ask Claude to create or edit profiles, clone existing ones, inspect your proxy library and launch browser sessions. You can also give it a list of clients and specify how their profiles should be named, grouped and tagged.
Unlike a basic CSV import, this approach lets you describe a sequence of related tasks and review the proposed changes as you work. It is useful for teams that want more control over profile setup without writing custom scripts for every task.
This guide focuses on the MCP approach. The aim is to use Claude to handle repetitive setup while keeping decisions about profile configuration, proxy assignment and team access under your control.
Know the Limits Before You Start
Before creating 50 profiles through MCP, account for a few operational limits:
- A maximum of 30 profiles per call. Divide 50 profiles into two batches, such as 25 and 25, rather than requesting all 50 in one operation.
- A maximum of 20 clones per call. If you're using a template profile, split cloning into smaller batches.
- Requests can be capped. If you request more items than a call supports, the extra items may be omitted without an explicit error. Verify the actual count after each operation.
- Profiles cannot be deleted through MCP. If you create unwanted profiles, you must remove them in the Incogniton app.
These limits make it important to work in batches, inspect the results and avoid sending large, loosely defined instructions to Claude.
Step-by-Step: Create 50 Client Profiles with Claude in Incogniton
To use this workflow, you'll need Incogniton V5, Node.js 18 or newer, and Claude Desktop or Claude Code configured to connect to the Incogniton MCP server. If you haven't set up the connection, start with the Incogniton MCP guide.
Step 1: Connect Claude to Incogniton
Generate an MCP token under Settings > Automation in Incogniton. Add the required MCP configuration to Claude Desktop or Claude Code, following the setup instructions, then restart the application if required.
Once connected, ask Claude to list your existing profiles. Check that it can retrieve the expected information before allowing it to make changes.
Treat the MCP token like a password. Anyone who obtains it may be able to access the capabilities it grants.
Step 2: Prepare your client list
Before creating profiles, organise the onboarding information into a table. At a minimum, include:
- Client name
- Platform or platforms
- Required number of profiles
- Client group
- Proxy region, if applicable
You can prepare this information in a spreadsheet and paste it into Claude. Check the list for duplicate entries, inconsistent client names, and missing information before proceeding.
This preparation matters because Claude can only work reliably with the instructions and data you provide. If the source list is inconsistent, automating it will not automatically fix the underlying problems.
Step 3: Build and test a template profile
Create one profile manually with your standard settings. Use it to establish the naming conventions and configuration you want to apply across the batch.
Test the profile before using it as a template. Keep Incogniton's fingerprint settings at their defaults unless you have a specific, legitimate reason to change them.
A tested template gives you a reference point for cloning and helps reduce differences between profiles. However, cloning is not a substitute for checking that each profile has the correct client-specific settings.
Step 4: Create client groups first
Ask Claude to create a group for each client before creating the profiles. For example:
"Using the client list below, create a profile group for each client. Use each client's name exactly as written. Check for existing groups with the same names first. Show me the proposed groups before creating them."
Review the list and confirm the changes. Creating the groups first gives you a clear structure for organising the profiles as they are created.
Step 5: Create profiles in batches
Once the groups are ready, ask Claude to create profiles according to your client list. Specify the naming convention, group, tags, and number of profiles required.
For example:
"Using the client table, create the required browser profiles in batches of 25. Name each profile using this format: Client – Platform – 01. Put each profile in the corresponding client's group and apply the platform name and onboarding tags. Do not create duplicate profiles. After each batch, report the number created and list any entries you could not process."
Review the first batch before proceeding with the second. If you are cloning a template instead, keep each cloning operation within the 20-profile limit.
After each batch, compare the profiles created against the original client list. Do not assume that a completed operation means every requested profile was created correctly.
Step 6: Automate proxy assignment
With the profiles in place, ask Claude to inspect your proxy library and propose assignments based on each client's requirements.
For example:
"List the proxies in my library, including their locations and identifiers. Match available proxies to the new profiles according to the required client regions. Show me a table containing each profile, its client group, proposed proxy, and proxy location. Flag missing, unavailable or duplicate assignments. Do not apply any changes until I approve the plan."
Check the proposed assignments before applying them. Confirm that each proxy meets the relevant client's requirements and that any restrictions on reuse are respected.
Also worth noting: search_profiles returns proxy usernames and passwords in plain text, so don't paste raw output into public files or screenshots.
Proxy assignment is an important checkpoint because an incorrect assignment can cause connection problems or undermine the separation you intended to maintain between client accounts. If your setup requires a dedicated proxy for each profile, make that requirement explicit rather than assuming Claude will infer it.
Step 7: Verify the completed setup
Once the profiles and proxies have been configured, ask Claude to retrieve the relevant details and compare them with your original client list.
For example:
"List every profile created for this onboarding batch, including its name, group, tags and proxy assignment. Compare the results with the original client table. Flag missing profiles, duplicate names, incorrect groups, missing tags, profiles without proxies and proxies assigned more than once. Summarise any discrepancies."
Resolve the discrepancies in Incogniton before giving the team access. Once a profile has been checked and its first login completed, update its status from onboarding to live or another status your team uses.
After Setup: Give the Team Access
Bulk creation handles the initial setup, but you still need to configure team access.
Use Incogniton's team management feature to assign the appropriate permissions to each teammate. Since profiles are grouped by client, you can use that structure to help organise access for account managers and other team members.
Before sharing a profile, confirm that the assigned user has the permissions required for their work and that the profile belongs to the correct client group.
Each profile may also require an initial login and platform verification. Complete these steps with an authorised team member, then check that the session works as expected before handing over the profile. A saved session can reduce repeated logins, but it does not guarantee that a platform will never request verification again.
Tips for Reliable Bulk Profile Creation with MCP
The difference between a useful automation workflow and a messy profile library often comes down to preparation and verification. These practices make bulk setup easier to repeat as your agency grows.
1. Give Claude a clear scope
Avoid asking Claude to set up everything at once. Break the workflow into separate tasks: inspect existing groups, create missing groups, create profiles, propose proxy assignments and verify the results.
For each task, specify what Claude should change, what it should leave untouched and what information it should report afterward. This reduces ambiguity and makes mistakes easier to identify.
2. Check existing profiles before creating new ones
Before each batch, ask Claude to check for existing profiles with the same names or client-platform combinations. This is particularly important when onboarding resumes after an interruption or when another teammate has already created some of the profiles.
If a profile already exists, ask Claude to flag it rather than creating a duplicate or changing its settings without approval.
3. Use one naming and tagging system
Choose a consistent naming convention, such as Client – Platform – Number, and use it across every batch. Agree on a fixed set of tags for platforms and workflow status, such as instagram, facebook, linkedin, onboarding, live and paused.
Include the approved names and tags in your prompts. Explicit rules make it less likely that different batches will end up with variations such as onboard, onboarding and new-client for the same status.
4. Keep a record of each batch
Maintain a simple onboarding tracker showing the requested profiles, creation status, group, proxy assignment and verification status. Update it after each batch.
This gives you a reference point if a call fails, the workflow is interrupted or a teammate needs to check what has already been completed. It also makes it easier to identify missing profiles without reviewing the entire library manually.
5. Review changes before applying them
Use a plan-and-confirm workflow for changes that affect multiple profiles, especially proxy assignment and edits to existing configurations. Ask Claude to show you the proposed changes first, then approve them only after checking the details.
Because MCP cannot delete profiles, prevention is particularly important. Start with a small test batch, inspect the results and expand to the remaining profiles only when the workflow behaves as expected.
6. Leave fingerprint settings alone unless necessary
Do not change browser fingerprint settings simply to make profiles look different. Use the defaults unless you have a specific requirement that justifies a change, and test any changes before applying them to a large batch.
The goal is a consistent, maintainable profile setup, not unnecessary configuration differences.
7. Protect your MCP token
Store the token securely and avoid pasting it into ordinary prompts, shared documents, or team chats. Limit access to the configuration to authorised users and rotate the token if you suspect it has been exposed.
Automation can save time, but it also makes it important to control who can perform actions through the connection.
Conclusion
To bulk create browser profiles for 50 clients, start with a clean client list, establish a tested template, create groups first, and use Claude to handle profiles and proxy assignments in manageable batches. Verify the results before giving your team access.
The main benefit is not just faster setup. It is a repeatable process that reduces manual work and makes client profiles easier to manage as your agency grows.
You can try Incogniton with 10 browser profiles free for two months and test the workflow before scaling up.
