Suralink MCP

Appearance

Suralink MCPModel Context Protocol server

Connect your AI assistant to Suralink engagements, request lists, files, and comments.

Getting Started
Browse Tools

Standard MCP over HTTP

Speaks the Model Context Protocol over the Streamable HTTP transport, so any MCP-aware client can connect.

OAuth sign-in

Deployed environments authenticate each request with an OAuth bearer token, discovered automatically by MCP clients.

Scope-aware tools

Tools appear only when your account holds the required access, so the assistant sees exactly what you can use.

Suralink connects audit and accounting firms with their clients to exchange request lists, files, and comments. The Suralink MCP server exposes that data to AI assistants through the Model Context Protocol, so a model can answer questions about engagements, request items, files, and comment history on your behalf.

The server exposes a single MCP endpoint plus a liveness probe:

RouteMethodPurpose
/mcpPOSTModel Context Protocol over Streamable HTTP
/healthGETLiveness probe — returns {"status":"ok"}

The MCP endpoint uses the official SDK's Streamable HTTP transport in stateless mode: every request gets a fresh server instance. There is no session cookie or persistent connection on the MCP side.

Continue to Getting Started to connect a client, or see the Tools reference for everything the server can do.