Set Up Pliant MCP
Turn on Pliant MCP for your organization, then connect your AI tool.
Jump to your tool: Claude | ChatGPT | Cursor | VS Code | Codex CLI | Antigravity CLI | Other clients | Pliant MCP Pro
Setup has three steps. Steps 1 and 2 happen once per organization, step 3 once per person.
| 🔛 1. Admin turns it on | 🔑 2. Get your credentials | 🔌 3. Connect your AI tool |
|---|---|---|
| Activate the Pliant MCP module in Pliant. | Find them in Pliant, or ask support. | Each member signs in with their own Pliant account. |
1. Turn on Pliant MCP (admin, one time)
MCP access is off by default. An admin turns it on in Settings > Modules by activating the Pliant MCP tile. Pliant MCP Pro is in early access, see below.
Deactivating a module later revokes access for everyone, across all connected AI tools. It does not delete conversation history already stored in those tools.
2. Get your credentials
Pliant MCP uses OAuth. What you need depends on the tool:
| Tool | You need |
|---|---|
| Claude, ChatGPT | Server URL, Client ID and Client Secret |
| Cursor, VS Code, Codex CLI, Antigravity CLI | Server URL and Client ID only. There is no secret. |
Your server URL is https://mcp.getpliant.com/mcp. Your Client ID and Client Secret are shown in Pliant, or contact Pliant support and we send them to you securely.
Treat the Client Secret like a passwordNever paste it into a chat, a ticket or a shared document.
3. Connect your AI tool
Not in the directories yetPliant is not yet in the Claude or ChatGPT connector directories, so you add it as a custom connector today. Once listed, you will pick it from the directory and skip the credentials step.
Claude
Works in Claude.ai, Claude Desktop and mobile (they share the connector).
Team or Enterprise (an Owner does this once)
- Open Organization settings > Connectors.
- Choose Add custom connector. Name it
Pliantand enter the server URL. - Open Advanced settings and enter the Client ID and Client Secret. Click Add.
- Optional: require approval for write tools such as
code_transaction,split_transactionandupdate_card.
Members then open Settings > Connectors, click Connect, sign in to Pliant and allow access.
Pro or Max (individual)
- Open Settings > Connectors and choose Add custom connector.
- Enter the server URL, then the Client ID and Client Secret under Advanced settings.
- Click Connect, sign in to Pliant and allow access.
Claude Code
claude mcp add --transport http pliant https://mcp.getpliant.com/mcpEnter the Client ID and Secret when prompted, then run /mcp to sign in.
Finally, enable the Pliant connector in the chat tools menu and ask: "Which Pliant account am I connected as?"
ChatGPT
For Business, Enterprise and Edu, a workspace admin sets this up. Pro and Plus users can use developer mode.
- Open Settings > Apps & Connectors > Advanced settings and enable Developer mode (or the workspace's custom connector permission).
- Choose Create. Name it
Pliant, use the server URL from above, and set authentication to OAuth. - Enter the Client ID and Client Secret. Leave scopes empty.
- After saving, ChatGPT shows a callback URL for this connector. If Pliant has not registered it yet, send it to support and wait for confirmation. Sign-in fails with "Callback URL mismatch" until then.
- Click Connect, sign in to Pliant and approve.
- In a chat, enable the Pliant connector from the tools menu.
Cursor
Public client: Client ID only.
-
Open Cursor Settings > MCP > Add new MCP server to edit
mcp.json. -
Add:
{ "mcpServers": { "pliant": { "url": "https://mcp.getpliant.com/mcp", "auth": { "CLIENT_ID": "<CLIENT_ID>" } } } } -
Click Connect on the
pliantserver, sign in and approve.
Cursor desktop listens on localhost:8787. If the browser shows a callback error, close other Cursor windows and retry.
VS Code
Public client: Client ID only. Works with GitHub Copilot Chat in agent mode.
-
Run MCP: Open User Configuration from the Command Palette and add:
{ "servers": { "pliant": { "type": "http", "url": "https://mcp.getpliant.com/mcp" } } } -
Start the
pliantserver. VS Code asks for a client ID: paste your Client ID and leave the secret empty. -
Sign in and approve.
If sign-in fails with "Callback URL mismatch", quit all VS Code windows, open one window and retry. VS Code needs port 33418 to be free.
Codex CLI
Public client: Client ID only.
-
At the top of
~/.codex/config.toml, above any[table], add:mcp_oauth_callback_port = 8977 mcp_oauth_callback_url = "http://127.0.0.1:8977/callback" -
Add the server:
codex mcp add pliant --url https://mcp.getpliant.com/mcp --oauth-client-id <CLIENT_ID> -
Sign in:
codex mcp login pliant
Use the URL exactly as shown, without a trailing slash. A different URL changes the callback and sign-in fails.
Antigravity CLI
Public client: Client ID only.
-
Add the server:
agy mcp add pliant https://mcp.getpliant.com/mcp -
In
~/.gemini/config/mcp_config.json, add to thepliantentry:"oauth": { "clientId": "<CLIENT_ID>" } -
Start
agy, run/mcp, choosepliantand Authenticate. -
Sign in and approve. The browser shows an authorization code. Copy it into the
agyprompt and nowhere else.
Any other MCP client
Pliant MCP is a standard remote HTTP MCP server with OAuth 2.1. Any client that supports remote MCP can connect.
| Property | Value |
|---|---|
| URL | https://mcp.getpliant.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with the Client ID (and Secret, if your client needs one) from Pliant |
Using a tool that is not listed here? Reach out to Pliant support and tell us which one. We will take a look.
Pliant MCP Pro (early access)
Pliant MCP Pro is a separate connector for customers who want specialized tools, for example issuing cards and other sensitive actions through MCP. It is in early access.
To use it:
- Reach out to Pliant support. We make the Pliant MCP Pro tile visible on your Modules page.
- An admin activates the tile in Settings > Modules.
- Add Pro as a second custom connector next to Pliant MCP, using the server URL, Client ID and Client Secret issued for Pro. They are different from your Pliant MCP credentials, and each public-client tool (Cursor, VS Code, Codex CLI, Antigravity CLI) needs its own Pro Client ID.
Pliant MCP Pro is not part of the AI tool directories. You always add it as a custom connector.
Check that it works
After connecting, ask: "Which Pliant account am I connected as?" You should see your name, organization and role.
Troubleshooting
| Problem | Fix |
|---|---|
| Sign-in fails immediately | You may have an open Pliant session in the browser. Open https://login.getpliant.com/v2/logout and retry. |
| "Callback URL mismatch" | See the notes for your tool above. For ChatGPT, send the callback URL to support. |
| The agent says a tool is unavailable | Check that an admin activated the module and that your role allows the action. |
| Access stops after a few minutes | Reconnect. If it repeats, send support your client name, version and the error text. |
Disconnect Pliant MCP
- In Pliant: My Account > Security and Devices > MCP Connections, then revoke the connection.
- In your AI tool: For Claude, Settings > Connectors > Pliant > Disconnect.
- Whole organization (admin): deactivate the module in Settings > Modules.
Related reading
Updated about 20 hours ago

