Skip to main content
GitHub Copilot supports MCP servers in agent mode, allowing you to connect TryPost directly to your VS Code workflow.

​
Prerequisites

  • VS Code with the GitHub Copilot extension installed
  • Copilot agent mode enabled
  • A TryPost Cloud account with an active trial or subscription (start a 7-day free trial)

​
Setup (IDE agent mode)

1

Create the MCP configuration file

In your project root, create or edit .vscode/mcp.json:
No Authorization header — Copilot uses VS Code’s MCP layer, which discovers OAuth from the URL.
2

Reload VS Code

Reload the window to load the new MCP configuration.
3

Sign in through your browser

Open Copilot Chat in agent mode. VS Code prompts you to sign in to TryPost. Approve the request in the browser and the server flips to Connected.
4

Verify the connection

Ask Copilot:
VS Code uses "servers" as the top-level key (not "mcpServers"). This is different from most other MCP clients.

​
Copilot coding agent (cloud)

GitHub’s coding agent (the one that runs on GitHub’s infrastructure to handle issues and PRs) does not yet support OAuth for remote MCP servers. TryPost’s MCP endpoint requires OAuth (mcp:use) and rejects Personal Access Tokens, so cloud coding agent MCP is not supported today. Use Copilot’s IDE agent mode (above) for MCP, or call the REST API from Actions / scripts with an API key from Settings → API Keys.

​
Global IDE configuration

To make TryPost available across all projects in your IDE, open the command palette and run MCP: Open User Configuration to add the server to your user-level settings.

​
Example prompts