mcp

MCP server combining PostgreSQL, Swagger/OpenAPI, and browser/frontend automation tools.

The Swagger side is designed as an execution layer for another agent:

• auth is managed inside MCP memory
• operation tools are generated from Swagger operationId
• consumers do not pass Authorization headers, API paths, or HTTP methods

The browser side is designed for frontend diagnostics and UI automation:

• stateful Playwright Chromium sessions
• screenshots and DOM/layout inspection
• frontend auth hydration via API login -> localStorage
• console and network diagnostics

Browser tool behavior

Registered browser tools:

• browser_open_session
• browser_close_session
• browser_navigate
• browser_auth_from_api_login
• browser_set_local_storage
• browser_seed_auth_state
• browser_open_profile_page
• browser_open_account_home
• browser_open_security_page
• browser_capture_profile_mobile
• browser_wait_for
• browser_click
• browser_fill
• browser_set_input_files
• browser_press
• browser_evaluate
• browser_get_text
• browser_get_attribute
• browser_screenshot
• browser_get_bounding_rect
• browser_get_computed_styles
• browser_assert_layout
• browser_save_storage_state
• browser_load_storage_state
• browser_get_console_logs
• browser_get_network_errors
• browser_inspect_page

Browser auth flow

Preferred frontend authentication flow:

1. Obtain API tokens using auth_login or browser_auth_from_api_login.
2. Write { accessToken, refreshToken, user: null } into frontend localStorage via browser_auth_from_api_login, browser_seed_auth_state, or browser_set_local_storage.
3. Navigate directly to the target authenticated route.

This avoids brittle UI-login dependencies and keeps browser automation stable.

Supported auth modes in high-level browser tools:

• apiLogin - perform API login and hydrate frontend auth state into localStorage
• useExistingMcpAuth - reuse an already authenticated MCP auth session (for example after auth_login)
• none - skip auth hydration entirely

Auth hardening notes:

• browser_auth_from_api_login and browser_inspect_page now return structured auth failures:
  • AUTH_API_LOGIN_FAILED
  • AUTH_REDIRECTED_TO_LOGIN
  • AUTH_SESSION_EXPIRED
• when a valid shared MCP auth session exists, browser auth can fall back to useExistingMcpAuth
• browser_set_local_storage works on an explicit origin and can optionally navigateToOrigin and/or reloadPage
• browser_seed_auth_state is a convenience wrapper for common auth objects like { accessToken, refreshToken, user }
• auth error payloads include:
  • finalUrl
  • debugScreenshotPath
  • debugHtmlPath

Browser file upload flow

browser_set_input_files supports:

• one or many files
• local disk paths
• in-memory files from text
• in-memory files from base64
• regular and multiple file inputs

Recommended input file descriptor shapes:

• local file path as plain string