Connect Fine Structure to GitHub Copilot and Copilot Studio

Yes, both Microsoft surfaces support remote MCP servers today, so neither needs a workaround. In VS Code you add a server to mcp.json and Copilot handles the OAuth flow in a browser window. In Copilot Studio you add it to an agent through the MCP onboarding wizard, whose dynamic discovery option matches how Fine Structure registers clients.

Before you start

Step by step

  1. VS Code: open the Command Palette and run MCP: Add Server, which adds a server to your workspace or user profile.
  2. VS Code: or write the file yourself at .vscode/mcp.json for one workspace, or in your user profile for everywhere, using the config snippet below with type http.
  3. VS Code: start the server and complete the sign in. VS Code handles the OAuth flow automatically and opens a browser window for authorization on the first connection.
  4. VS Code: switch Copilot to agent mode and ask it to list your Fine Structure apps.
  5. Copilot Studio: open the Tools page for your agent, select Add a tool, then New tool, then Model Context Protocol to open the MCP onboarding wizard.
  6. Copilot Studio: fill in Server name, Server description and Server URL, using https://finestructure.ai/api/mcp. Write the description carefully, because the agent orchestrator uses it to decide whether to call the server.
  7. Copilot Studio: choose OAuth 2.0 as the authentication type, then Dynamic discovery, which is the option for servers supporting dynamic client registration with a discovery endpoint. Fine Structure publishes that metadata, so no client ID, secret or endpoint is needed.
  8. Copilot Studio: select Create, then Next, then on Add tool select Create a new connection, then Add to agent.

Configuration

{
  "servers": {
    "finestructure": {
      "type": "http",
      "url": "https://finestructure.ai/api/mcp"
    }
  }
}

What to watch out for

Questions people ask

Does VS Code Copilot support remote MCP servers, or only local ones?

Both. VS Code's MCP configuration reference documents a remote server with type http and a url, and states that VS Code handles the OAuth flow automatically by opening a browser window on the first connection.

Which Copilot Studio authentication option should I pick?

OAuth 2.0 with Dynamic discovery. That is the option for servers supporting dynamic client registration with a discovery endpoint, which is what Fine Structure publishes. Manual is the wrong choice, because it expects a fixed client ID and secret.

Will my organization's data policies block this?

They might. Microsoft documents that MCP access in Copilot Studio relies on Power Platform connectors, so a data policy regulating connectors also regulates this server and its tools. Check with whoever owns those policies first.

Vendor documentation we checked

All platforms: connect Fine Structure to any AI. Also the documentation and pricing.