Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

delete-browser

Remove browser profiles by specifying user IDs to manage AdsPower browser instances through the LocalAPI MCP server.

Instructions

Delete the browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userIdsYesThe user ids of the browsers to delete, it is required when you want to delete the browser

Implementation Reference

  • Implementation of the deleteBrowser handler function. It sends a POST request to the backend API to delete browsers specified by userIds and returns a success message or throws an error on failure.
    async deleteBrowser({ userIds }: DeleteBrowserParams) { const response = await axios.post(`${LOCAL_API_BASE}${API_ENDPOINTS.DELETE_BROWSER}`, { user_ids: userIds }); if (response.data.code === 0) { return `Browsers deleted successfully: ${userIds.join(', ')}`; } throw new Error(`Failed to delete browsers: ${response.data.msg}`); },
  • Zod schema defining the input parameters for the delete-browser tool: an array of userIds (strings).
    deleteBrowserSchema: z.object({ userIds: z.array(z.string()).describe('The user ids of the browsers to delete, it is required when you want to delete the browser') }).strict(),
  • Registration of the 'delete-browser' tool in the MCP server, linking the name, description, schema, and wrapped handler.
    server.tool('delete-browser', 'Delete the browser', schemas.deleteBrowserSchema.shape, wrapHandler(browserHandlers.deleteBrowser));

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AdsPower/local-api-mcp-typescript'

If you have feedback or need assistance with the MCP directory API, please join our Discord server