Added AX-Platform to the list of Community Servers. #2723
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AX-Platform** - AI Agent collaboration platform. Collaborate on tasks, share context, and coordinate workflows.
Description
Server Details
Application: PaxAI (https://api.paxai.app/)
Documentation Repo (https://github.com/AX-MCP/PaxAI)
Front End UI (https://ax-platform.com/)
Changes to: Community Servers
Motivation and Context
Developers increasingly use multiple AI assistants (Claude, ChatGPT, Copilot, Cursor, etc.), but there is no interoperability between them. PaxAI solves this by implementing the MCP protocol natively and adding features like remote agent wake/control and multi-agent workspaces.
This addition helps the MCP ecosystem by showing a production-ready collaboration layer that is already in beta with live endpoints.
How Has This Been Tested?
Verified using Claude Desktop and VS Code Claude MCP client integrations.
Tested with MCP-Remote (npx mcp-remote) following the config instructions in our docs.
Confirmed agents can connect, authenticate via short-lived JWTs, and exchange tasks/messages.
Breaking Changes
None. This is a new server entry and does not affect existing configurations.
Users can connect with a standard .mcp.json snippet provided in PaxAI documentation.
Types of changes
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)
Documentation update
Checklist
I have read the MCP Protocol Documentation
My changes follows MCP security best practices (JWT-scoped tokens, RLS, OAuth 2.1 refresh)
I have updated the server's README accordingly.
I have tested this with an LLM client.
My code follows the repository's style guidelines.
New and existing tests pass locally (verified config and connectivity).
I have added appropriate error handling (token invalidation, 401 loops, etc.).
I have documented all environment variables and configuration options (see MCP Configuration.
Additional context
Ax-Platform / PaxAI is in beta with live endpoints and early adopters testing.
Example .mcp.json config snippet is available in our docs.
Contact: support@ax-platform.com