KosmoKrator

productivity

BrowserStack MCP Gateway for AI Agents

Expose BrowserStack tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

BrowserStack MCP Gateway

Expose BrowserStack to MCP clients with `kosmokrator mcp:serve --integration=browserstack`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server.

Install KosmoKrator 
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
Install gateway entry 
kosmokrator mcp:gateway:install --integration=browserstack --write=deny --json
MCP configuration 
{
  "mcpServers": {
    "kosmokrator-browserstack": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=browserstack",
        "--write=deny"
      ]
    }
  }
}
Serve manually 
kosmokrator mcp:serve --integration=browserstack --write=deny

Client Notes

Use one scoped MCP gateway entry, then adapt the config location to the client or framework.

Claude Code Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry. Claude Code can launch the local kosmo binary directly from the project MCP config.
Cursor Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server. Use the same KosmoKrator install and integration credentials that power terminal and headless runs.
Codex Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy. Keep write access denied or ask-based unless the workspace is trusted.
OpenAI Agents SDK Attach KosmoKrator integration tools to OpenAI Agents SDK workflows through a local MCP gateway. Use headless JSON commands for CI-style execution and MCP for agent tool discovery.
Claude Agent SDK Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server. Use a narrow integration list so the agent does not load unrelated tools.
Vercel AI SDK Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts. Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.
LangChain Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls. Keep the gateway scoped to the integration and operation class needed by the chain.
LangGraph Run KosmoKrator integration calls from LangGraph nodes while preserving local credentials and permissions. Headless CLI calls fit repeatable graph edges; MCP fits exploratory agent nodes.
CrewAI Expose KosmoKrator integrations to CrewAI workers as scoped local tools. Use per-worker integration scopes to avoid giving every worker every tool.
Generic MCP Clients Connect any stdio-compatible MCP client to local KosmoKrator integration tools. Start with read-only write policy and expand only for trusted projects.

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names.

MCP toolSource functionType
integration__browserstack__browserstack_get_plan browserstack.browserstack_get_plan Read read
integration__browserstack__browserstack_list_browsers browserstack.browserstack_list_browsers Read read
integration__browserstack__browserstack_list_projects browserstack.browserstack_list_projects Read read
integration__browserstack__browserstack_get_project browserstack.browserstack_get_project Read read
integration__browserstack__browserstack_update_project browserstack.browserstack_update_project Write write
integration__browserstack__browserstack_delete_project browserstack.browserstack_delete_project Write write
integration__browserstack__browserstack_list_builds browserstack.browserstack_list_builds Read read
integration__browserstack__browserstack_update_build browserstack.browserstack_update_build Write write
integration__browserstack__browserstack_delete_build browserstack.browserstack_delete_build Write write
integration__browserstack__browserstack_delete_builds browserstack.browserstack_delete_builds Write write
integration__browserstack__browserstack_list_build_sessions browserstack.browserstack_list_build_sessions Read read
integration__browserstack__browserstack_get_session browserstack.browserstack_get_session Read read
integration__browserstack__browserstack_update_session browserstack.browserstack_update_session Write write
integration__browserstack__browserstack_delete_session browserstack.browserstack_delete_session Write write
integration__browserstack__browserstack_get_session_logs browserstack.browserstack_get_session_logs Read read
integration__browserstack__browserstack_get_session_network_logs browserstack.browserstack_get_session_network_logs Read read
integration__browserstack__browserstack_upload_app browserstack.browserstack_upload_app Write write
integration__browserstack__browserstack_list_recent_apps browserstack.browserstack_list_recent_apps Read read
integration__browserstack__browserstack_delete_app browserstack.browserstack_delete_app Write write
integration__browserstack__browserstack_api_get browserstack.browserstack_api_get Read read
integration__browserstack__browserstack_api_post browserstack.browserstack_api_post Write write
integration__browserstack__browserstack_api_put browserstack.browserstack_api_put Write write
integration__browserstack__browserstack_api_delete browserstack.browserstack_api_delete Write write

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.