Postman
Test and debug the Links MCP Server using Postman.
Because the Links MCP Server follows the standard Model Context Protocol (HTTP/SSE), you can connect to it directly using Postman without any local adapters or npx scripts.
This is the best way to debug connection issues or inspect raw JSON-RPC responses.
Prerequisites
Connection Setup
Configure Connection
Open the MCP Client in Postman and configure the connection details:
- Transport Type:
SSE(Server-Sent Events) - Base URL:
https://dev-backend.thelinks.ai/api/v1/mcp
Add Authentication
The server requires a Bearer token to authorize access to your financial data.
- Key:
Authorization - Value:
Bearer <YOUR_MCP_KEY_OR_BEARER_TOKEN>
Note
Make sure to include the word Bearer followed by a space before your key.
Connect
Click the Connect button.
Postman will establish a handshake with the Links server. Once connected, the interface will automatically populate the list of available tools (e.g., get-chart-of-accounts, get-accounting-periods) in the middle panel.
Executing Tools
Once connected, you can interact with your data immediately.
Select a Tool
Click on a tool from the list (e.g., search-account-by-name).
The Payload section will automatically update to show the required fields for that specific tool.
Fill Arguments
Enter the values for the arguments. For example, if searching for a Chart of Account (COA) by name:
{
"name": "Cash"
}Run & Inspect
Click Run Tool.
The result will appear in the output panel, showing the real data fetched from the Links Platform.
Why is this different from Claude?
Claude Desktop cannot make direct HTTPS requests to remote servers on its own yet. It relies on a local "bridge" script (npx ...) to handle the connection.
Postman acts as a direct HTTP client, so it speaks directly to your MCP using standard Headers and Bodies.