Test Cotality MCP interactively in your browser — connect, list the tools your token is scoped for, and run tool calls without writing any code.
MCP inspector is an open-source browser-based tool for testing MCP servers interactively. It lets you connect to Cotality MCP, discover your available tools, and execute tool calls — all without writing any code.
While MCP inspector is one of the most widely adopted tools for MCP server testing and debugging, it is a third-party open-source project not maintained by Cotality. It is intended solely for local development and testing purposes and should not be used in production environments.
Setup
Prerequisites
MCP inspector runs on Node.js. If you don’t already have it installed:
Download the latest LTS (Long-Term Support) version of Node.js
Run the installer and follow the on-screen prompts — the default settings are fine
Open a terminal (macOS: Terminal, Windows: Command Prompt or PowerShell) and verify the installation:
node --version
You should see a version number (e.g., v22.x.x). This confirms that Node.js — and its bundled tools npm and npx — are ready to use.
Launch MCP inspector
Run the following command in your terminal:
npx @modelcontextprotocol/inspector
If prompted to install the package, type y and press Enter to confirm.The inspector should automatically open in your default web browser. If it doesn’t, check your terminal for the displayed URLs and open the one that includes the authentication token — this will take you directly to the Inspector UI with the connection pre-configured.
Connect to Cotality MCP
In the inspector UI, set the Transport type to Streamable HTTP.
Enter the Cotality MCP endpoint URL for your target environment:
Environment
URL
UAT
https://mcp-uat.cotality.com/mcp
Production
https://mcp.cotality.com/mcp
Click the Authentication tab in the left sidebar and configure the following:
Header name — Authorization
Header value — Bearer <your_token>
Replace <your_token> with your OAuth2 access token. See Authentication for how to obtain one.
Click Connect.
Discover tools
Once connected, go to the Tools tab and click List tools. The inspector displays all tools available to you, including their names and descriptions. To see the detailed input/output schemas that an agent receives upon connecting, expand the tools/list call in the History section of the UI.
Execute a tool call
Select a tool from the list (e.g., clip-find_property_by_address).
Fill in the input parameters using the auto-generated form.
Click Run tool.
The response JSON is displayed in the results panel.
This is the fastest way to explore Cotality MCP’s capabilities and verify that your credentials are working correctly.
MCP inspector maintains a session log under History which is useful for understanding and debugging MCP request/response sequences.
Troubleshooting
Problem
Solution
Connection fails
Verify your endpoint URL and that your access token hasn’t expired. Request a new token if needed.
401 Unauthorized
Ensure the authorization header is populated using the prefix “Bearer” and that your token hasn’t expired. Follow the Authentication steps to obtain a fresh token.
429 Too many requests
You have exceeded a request quota — 60 requests per minute per client_id by default, and 25 requests per minute per signed-in user on the PKCE flow. The gateway sends no Retry-After header, so back off exponentially using your own timer. See Rate limits.
A tool is missing from the list
tools/list only returns tools your token is scoped for. Contact your account team if the scope is missing.
Tool call returns an error object
Read the code and retryable fields. Only retry when retryable is true. See MCP tool errors.