Connecting

The Paxper MCP server is available at:

https://api.paxper.com/api/v1/mcp

Claude.ai

1. Go to Settings → Connectors → Add custom connector.
2. Enter the MCP server URL above.
3. Click through the login flow with your Paxper account, pick the organization you want to connect, and click Allow.

Claude Desktop

Add the connector from Settings → Connectors → Add custom connector the same way as on claude.ai. You’ll be redirected to log in and approve access in your browser.

Claude Code

claude mcp add --transport http paxper https://api.paxper.com/api/v1/mcp

Claude Code opens a browser window for the login and consent screen the first time it uses the connector.

OpenAI Codex (CLI and IDE extension)

1. Add the server:

codex mcp add paxper --url https://api.paxper.com/api/v1/mcp

2. Log in. Codex opens a browser window for the login and consent screen:

codex mcp login paxper

3. Check that the server is listed with codex mcp list.

The Codex IDE extension shares the same config.toml, so the server is available there too.

Official docs: Model Context Protocol – Codex 

Gemini CLI

Add the server to settings.json:

{
	"mcpServers": {
		"paxper": {
			"httpUrl": "https://api.paxper.com/api/v1/mcp"
		}
	}
}

Start Gemini CLI. The first time it uses the server, it opens a browser window for the login and consent screen. If it doesn’t, run /mcp auth paxper.

Official docs: MCP servers with the Gemini CLI 

Not covered yet

These clients don’t have steps on this page yet:

• Cursor: its docs describe remote OAuth only with a pre-registered client ID and secret. Paxper issues client registrations dynamically, so the flow can’t be completed from those docs.
• VS Code (GitHub Copilot): its docs explain how to add a remote HTTP server, but not how OAuth sign-in works for one.
• ChatGPT: plan availability for custom connectors differs between sources, and the official help center page couldn’t be checked.

Other MCP clients

Other MCP clients that support remote servers with OAuth and https or localhost redirects (for example MCP Inspector) can connect using the same server URL. Add it as a custom/remote MCP server pointing at https://api.paxper.com/api/v1/mcp and follow the client’s own OAuth flow — it will redirect you to Paxper to log in and approve access.

The login and consent screen

Every client goes through the same flow the first time it connects:

1. Log in with your Paxper account (or you’ll already be logged in if you have an active session).
2. Choose which organization to connect. A connection is bound to a single organization — if you belong to more than one, pick the one you want this assistant to work with.
3. Click Allow.

To connect the same assistant to a different organization, disconnect it and connect again, choosing the other organization at the consent screen.

Disconnecting

Go to Settings → Connected Apps in Paxper to revoke a connection. Organization admins can also disconnect any member’s connection from the same page — useful when someone leaves the team or a connection looks suspicious.