Manage AntiLogin Through MCP
The MCP server lets you connect an AI agent to AntiLogin and give it controlled access to app features. Through MCP, an agent works with AntiLogin objects, not only with an open browser page.
What an Agent Can Do
Within its granted permissions, an agent can:
- retrieve profile information;
- create and edit profiles;
- launch and stop browser sessions;
- work with tags and proxies;
- retrieve the automation port of a running profile for further work through CDP.
Connect an Agent
- Open AntiLogin account settings and go to MCP settings.
- Create an MCP client and choose the permissions the agent needs.
- Add the generated configuration to the agent's MCP client.
- Give the agent a task, such as creating a profile, assigning a proxy, launching a profile, or stopping a session.
The agent receives only the MCP permissions you select and the permissions granted to your role in the current workspace. AntiLogin requests approval for certain actions.
MCP and CDP: the Difference
MCP manages AntiLogin features: profiles, tags, proxies, and browser sessions. A CDP port gives access to the already running browser for a specific profile and lets you perform actions inside websites.
Use MCP when you need to manage profiles in the app. Use CDP or Playwright when you need to perform actions in a profile's browser. For details, see Browser Automation.