Petrora

GUIDES · TEXAS · CONNECT

Connect Copilot, Cursor, and other MCP clients

How to add Petrora's MCP server to Microsoft Copilot Studio, Cursor, VS Code, and any other client that supports remote MCP servers.

UPDATED OCT 29, 2026

Petrora speaks MCP over streamable HTTP at https://mcp.petrora.com/mcp. Any client that can add a remote MCP server can use it. The pages for Claude and ChatGPT cover the two most common; this page covers the rest.

Status: beta, free trial. The endpoint is live for every account; the free trial starts the first time you connect or create a key, no credit card required (how it works). Clients sign in through the connector's OAuth flow when they first connect: a Petrora page opens in your browser, you approve, and you are sent back. Clients that cannot open a browser can send an API key from your account page as the bearer token instead.

Microsoft Copilot

Microsoft 365 Copilot reaches external tools through agents built in Copilot Studio. To give an agent Petrora:

  1. In Copilot Studio, open or create an agent.
  2. Go to Tools (called Actions in older versions) and choose Add a tool, then Model Context Protocol.
  3. Enter the server URL https://mcp.petrora.com/mcp and the authentication Petrora provides.
  4. Publish the agent to Microsoft 365 Copilot or Teams.

Your tenant admin controls whether custom MCP connections are allowed.

Cursor

Add to Cursor's MCP settings (Settings, MCP, Add new global MCP server), or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "petrora": {
      "url": "https://mcp.petrora.com/mcp"
    }
  }
}

VS Code with GitHub Copilot

Add to .vscode/mcp.json in a workspace:

{
  "servers": {
    "petrora": {
      "type": "http",
      "url": "https://mcp.petrora.com/mcp"
    }
  }
}

VS Code will prompt for authorization the first time a tool is called.

Any other client

The server follows the MCP specification's streamable HTTP transport with OAuth 2.1 for authorization, and also accepts a bearer API key in the Authorization header for clients that cannot run an OAuth flow. If your client asks for a "command" rather than a URL, it expects a local server; use a bridge such as mcp-remote:

npx mcp-remote https://mcp.petrora.com/mcp

Without MCP

If your tooling cannot speak MCP, the plain REST API returns the same data as JSON and needs nothing but an HTTP client. Its contract is an OpenAPI 3.1 document:

https://api.petrora.com/v1/openapi.json

That document is what most agent frameworks, action builders, and client generators consume. LangChain's OpenAPI toolkit, Vercel's AI SDK tool helpers, and any OpenAPI-driven function-calling setup can load it and expose every endpoint as a tool. openapi-generator, orval, and openapi-typescript produce typed clients from it. The interactive reference renders the same document with a try-it client, and the written API reference covers the identifiers, windows, and lags that a generated client will not explain.