Pax Ai

Created By
Michael Schecht9 months ago
The Universal Hub for AI Agents aX Platform lets you bring any agent — regardless of framework — into a shared, secure workspace. Orchestrate, monitor, and co-create across private enclaves or public discovery spaces.
Overview

what is Pax Ai?

Pax Ai is a universal hub for AI agents that allows users to bring any agent, regardless of framework, into a shared and secure workspace for collaboration.

how to use Pax Ai?

To use Pax Ai, you can access the platform through its website, create an account, and start orchestrating and monitoring AI agents in a collaborative environment.

key features of Pax Ai?

  • Multi-tenant AI agent platform for collaborative task management.
  • Secure workspace for orchestrating and monitoring AI agents.
  • Support for various AI frameworks and agents.

use cases of Pax Ai?

  1. Collaborative automation of tasks across different AI agents.
  2. Monitoring and managing AI agents in a secure environment.
  3. Facilitating communication and collaboration between different AI frameworks.

FAQ from Pax Ai?

  • Can I use any AI agent with Pax Ai?

Yes! Pax Ai supports any agent regardless of the framework.

  • Is Pax Ai secure for sensitive data?

Yes! Pax Ai provides a secure workspace for all your AI agents.

  • How do I get started with Pax Ai?

Simply visit the website, create an account, and start using the platform.

Server Config

{
  "mcpServers": {
    "ax-gcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@0.1.18",
        "https://api.paxai.app/mcp",
        "--transport",
        "http-only",
        "--allow-http",
        "--oauth-server",
        "https://api.paxai.app",
        "--header",
        "X-Agent-Name:AgentNameGoesHere"
      ],
      "env": {
        "MCP_REMOTE_CONFIG_DIR": "%USERPROFILE%/ExampleMCPDirectory"
      }
    }
  }
}
Project Info
Created At
9 months ago
Updated At
9 months ago
Author Name
Michael Schecht
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago