Authentication
Use a client that supports OAuth authorization for remote MCP servers. The client follows the server’s advertised discovery and authorization metadata, starts the authorization code flow with PKCE, and sends a bearer token with MCP requests. The Exterview sign-in page offers the options configured for your workspace. These can include Microsoft sign-in or an Exterview email and password. The access token identifies the workspace and caller.exterview:read is the read scope. Some deployments can grant exterview:write separately. Review the scopes actually granted, and request the minimum access needed. Follow the client’s reauthorization flow when a grant expires or changes.
Discover and call tools
Use an MCP SDK for Streamable HTTP. The gateway accepts MCP requests over HTTPS POST at the issued endpoint and uses JSON responses. Let the client negotiate the protocol version and handle authorization.- Send
initializeand complete the initialization handshake. - Send
tools/listand follownextCursorif discovery returns one. Use the returned names and input schemas for your connection. - Send
tools/callwith the exact name and matching arguments. Reuse record IDs returned by earlier calls. Read the result content and check for errors before using any data.
list_jobs.
Content-Type: application/json and Accept: application/json, text/event-stream. The current gateway returns tool payloads as JSON text in the MCP result content. Use the discovered schema for exact inputs and the tool catalog to browse available workflows.
Errors and limits
Use tool-specific page limits and opaque cursors. Request only the fields and scope needed for the workflow. A successful connection does not guarantee access to every record or tool. Share the correlation ID, if present, when escalating through your organization’s support channel.

