GitHub Copilot SDK connector for Power Platform

January 26, 2026

GitHub Copilot SDK brings the Copilot CLI agent runtime to Python, TypeScript, Go, and .NET. You define agent behavior and tools. Copilot handles planning, calls tools, edits files, and routes models over JSON-RPC to the Copilot CLI in server mode. Add Work IQ work context, Copilot plugins or MCP servers, and local files so Copilot grounds answers in your organization’s knowledge—owners, specs, meeting transcripts, and design docs. The SDK inherits that context and toolchain.

This connector bridges that SDK into Power Platform with MCP-friendly JSON-RPC tools. Keep auth local, add DLP and approvals, and orchestrate Copilot agents from flows, apps, or Copilot Studio—without desktop control or computer-use sessions.

What is the GitHub Copilot SDK connector?

MCP-compliant Power Platform custom connector that proxies JSON-RPC calls to the GitHub Copilot SDK through a Cloudflare Tunnel. It reuses your local Copilot authentication and exposes tools to manage sessions, send prompts, list models, and check status.

Why this matters

• Orchestrate GitHub Copilot SDK sessions from Power Automate, Power Apps, or Copilot Studio
• Keep auth local—no secrets in the connector
• Reuse JSON-RPC tools in flows, apps, or agents

Use case: alternative to Copilot Studio computer-use

• Keep AI actions inside Power Platform scopes and connectors (DLP, approvals, logging)
• Use explicit JSON-RPC tools with typed arguments instead of full desktop control
• Run the SDK locally—no remote desktop or screen control
• Pair with Power Automate RPA for desktop steps when needed

Comparison

Architecture

Power Platform → Cloudflare Tunnel → localhost:3000 → GitHub Copilot SDK

Setup

1. Install dependencies

   cd "GitHub Copilot SDK"
   npm install
   

2. Start the proxy server

   npm start
   # or
   node proxy-http-to-sdk.mjs
   

3. Start Cloudflare Tunnel

   cloudflared tunnel --url http://localhost:3000
   

   Copy the generated URL (e.g., https://abc-xyz.trycloudflare.com).

4. Update the connector script (script.csx)

   private const string DefaultSdkUrl = "https://abc-xyz.trycloudflare.com/jsonrpc";
   

5. Deploy to Power Platform

   pac connector update --environment <env-id> --connector-id <connector-id> --script-file script.csx
   

Copilot Studio setup

1. Import the connector into your environment (apiDefinition.swagger.json, apiProperties.json, script.csx).
2. In Copilot Studio, go to Tools → Add a tool → Model Context Protocol.
3. Set the endpoint to your tunnel URL + /jsonrpc.
4. Optional: Add environment variables for default model/session naming; keep secrets empty (auth is local).
5. Apply DLP and approvals in the environment for guardrails.

Agent instruction

Maintain one Copilot SDK session per conversation. If missing, call copilot_create_session with sessionId = conversationId and model. Use copilot_send to answer user requests. Use copilot_list_sessions to reuse sessions; clean up with copilot_delete_session.

Tool calling pattern (Copilot Studio)

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "id": 1,
  "params": {
    "name": "copilot_send",
    "arguments": {
      "sessionId": "conversation-id",
      "prompt": "draft an email about ..."
    }
  }
}

Tools

Note: Copilot CLI defaults to --allow-all, enabling file system and git tools. Configure SDK client tools to disable or limit, or run CLI with restricted tools. This connector forwards JSON-RPC; it does not add extra sandboxing.

Example: create session

{
  "jsonrpc": "2.0",
  "method": "tools/call",
  "id": 1,
  "params": {
    "name": "copilot_create_session",
    "arguments": {
      "model": "claude-sonnet-4",
      "sessionId": "my-session"
    }
  }
}

Authentication

Uses your local GitHub Copilot auth. Verify with:

copilot auth status

Troubleshooting

Files

Guardrails and safety

• Use a named/persistent tunnel and restrict access; avoid exposing publicly without auth
• Keep the connector in a locked-down environment; enforce DLP and approvals
• File access: CLI defaults to file system/git tools; restrict tools in the SDK client or CLI, and audit outputs
• Log tool calls (flows) and add retries/timeouts in proxy-http-to-sdk.mjs
• For desktop actions, pair with Power Automate RPA rather than exposing the desktop

Limitations

• No direct desktop automation; you must wire actions through flows/apps
• Tunnel URLs rotate unless you use a named tunnel
• SDK sessions persist locally; clean up with copilot_delete_session

Tips

• Use a named/persistent Cloudflare Tunnel to avoid URL changes; update DefaultSdkUrl when it changes
• Run the proxy where file access is appropriate; treat it as a privileged process
• Clean up sessions with copilot_list_sessions + copilot_delete_session
• Add logging/telemetry (for example, Application Insights) if you need observability

Resources

• Connector repo: SharingIsCaring/GitHub Copilot SDK
• GitHub Copilot SDK docs: https://docs.github.com/en/copilot/building-copilot-extensions/github-copilot-sdk
• GitHub Copilot SDK repo: https://github.com/github/copilot-sdk
• Copilot CLI docs: https://docs.github.com/en/copilot/github-copilot-cli
• Copilot plugin marketplace: /plugin marketplace (see Copilot CLI; docs: https://aka.ms/copilot-cli-plugins)
• Work IQ MCP server: https://aka.ms/WorkIQMCP