Pliant Developer MCP

📘

For developers building on Pliant

Developer MCP gives your AI coding assistant the reference of the Pliant Program API or the Payment API. It does not connect to your Pliant organization or your data, and it cannot call the APIs for you.

Why use it

When you integrate the Pliant API, your coding assistant has to guess how it is structured unless it can read the reference. Developer MCP lets it look up the API while it writes code:

• Which endpoint does what. Browse every path and method with a short summary.
• Exact request and response shapes. Parameters, enums, required fields and security schemes, taken from the current API specification instead of from memory.
• Find the right endpoint fast. Search across paths, operations and parameters, for example "which endpoints deal with receipts".

The result is code that matches the real API, with fewer wrong endpoint names and invented fields.

📘

Looking for Pliant MCP?

To ask questions about your spend, receipts or cards, you need Pliant MCP, not Developer MCP. See the Pliant MCP Overview for how the servers differ.

What it can do

Each server covers one API reference. It does not make API calls and never touches your data.

Get access

Developer MCP is protected. To get access, reach out to Pliant support. If you are integrating with Pliant, your solution engineer will also share it with you.

There is one server per API:

Use the one that matches the API you integrate with, or add both. The same access key works for both.

You receive an access key. Send it in the x-readme-auth header, as the plain value without a Bearer prefix.

❗

Keep the access key private

Treat it like a password. Never paste it into a chat, a ticket or a shared document, and do not commit it.

Cursor

{
  "mcpServers": {
    "pliant-program-api": {
      "url": "<SERVER_URL>",
      "headers": { "x-readme-auth": "<ACCESS_KEY>" }
    }
  }
}

Claude Code

claude mcp add --transport http pliant-program-api <SERVER_URL> --header "x-readme-auth: <ACCESS_KEY>"

Other clients

Any client that supports remote HTTP MCP servers can connect to the server URL and send the access key in the x-readme-auth header. Replace <SERVER_URL> in the examples above with the URL from the table.

Try it

• "Which endpoints deal with receipts, and what does each one do?"
• "Show me the request body for uploading a receipt."
• "Explain how to list transactions with pagination, based on the API reference."
• "Write a client function that uploads a receipt, using the exact parameters from the API reference."

Related

• Pliant MCP Overview
• Set Up Pliant MCP