> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp.md). # Remote OAuth MCP OAuth Remote MCP configuration enables secure authentication between MCP clients and the OvalEdge MCP server using an external OAuth identity provider. It allows clients such as Cursor, Claude, VS Code, and Microsoft Copilot Studio to authenticate users before accessing MCP tools. The MCP server is configured with `AUTH_MODE=remote` to support remote OAuth authentication. OAuth client details, authorization endpoints, token endpoints, and redirect URLs are configured based on the selected client and identity provider. This configuration ensures that authenticated requests are securely validated before MCP tools and governed data are accessed. The following are the supported **Remote OAuth MCP configurations**: * [Cursor](https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-cursor-using-remote-oauth) * [Claude](https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-claude-desktop-using-remote-oauth) * [VS Code](https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-vs-code-github-copilot-using-remote-oauth) * [Microsoft Copilot Studio](https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp/set-up-microsoft-copilot-studio-using-remote-oauth) *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.1/mcp-server/deployment-options/remote-mcp/remote-oauth-mcp.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.