GitHub Copilot, Microsoft 365 & Other Agents

Overview

Postnomic's MCP server isn't tied to any one client. Any MCP-capable agent that supports remote (Streamable HTTP) MCP servers with a bearer token can connect — GitHub Copilot, Microsoft 365 Copilot / Copilot Studio, and a growing list of other assistants all speak the same protocol. The diagram below shows the shape that's common to every one of them: the agent holds a Personal Access Token (PAT), sends it as a bearer credential to the Postnomic MCP server, and the server forwards it unchanged to the API — exactly as it does for Claude Code or any other local agent.

Whichever agent you use, the connection reduces to two facts: the server URL

https://mcp.postnomic.com/mcp

and a bearer Personal Access Token. If you haven't minted one yet, see Connect a Local Agent (Personal Access Token) — that article covers what a PAT is, how to create one from the dashboard, and how to treat it securely. Come back here once you have a pnp_… value in hand.

A note on exact steps. GitHub Copilot, Microsoft 365 Copilot, and other agent platforms ship new MCP-configuration UIs frequently, and menu names and screens can and do change between releases. The instructions below describe the current shape of each flow as accurately as we can, but treat the menu labels as approximate — the URL and the bearer-token requirement are the parts that stay constant, and are what to search each platform's own MCP/tools documentation for if a screen doesn't match what's described here.

GitHub Copilot

GitHub Copilot's agent mode (in VS Code, Visual Studio, and other Copilot-enabled editors) can call tools from a remote MCP server. In broad strokes:

Open your editor's MCP server configuration — in VS Code this is typically an mcp.json file or the MCP: Add Server command from the Command Palette; other Copilot surfaces expose an equivalent "Add MCP Server" entry in their agent/tools settings.
Add an HTTP-transport server entry pointing at:
```
https://mcp.postnomic.com/mcp
```
Configure the request header:
```
Authorization: Bearer pnp_...
```
substituting the token you copied when you minted your PAT.
Save and reload/reconnect the MCP server in Copilot's tools panel. Postnomic's tools (listing blogs and posts, publishing, reading analytics, and the rest — see the MCP Tools Reference article) should appear alongside any other MCP servers you've configured.

Because Copilot reads the same .mcp.json-style shape most HTTP MCP clients use, the generic snippet under Other agents below is a safe fallback if your Copilot surface's configuration screen looks different from what's described above.

Microsoft 365 Copilot / Copilot Studio

Microsoft 365 Copilot and Copilot Studio support connecting external tools through custom connectors, including MCP servers over Streamable HTTP. The overall flow:

In Copilot Studio (or the Microsoft 365 admin surface used to register agent tools), create a new custom connector / tool and choose the MCP / Streamable HTTP transport option.
Set the server URL to:
```
https://mcp.postnomic.com/mcp
```
Configure authentication as a bearer token / API key style header:
```
Authorization: Bearer pnp_...
```
using your Postnomic PAT.
Publish or enable the connector for the Copilot agent or environment you want to grant access to, then test it — the same tools available to any other MCP client (blogs, posts, publishing, translations, images, analytics) should be callable from the Copilot conversation.

Microsoft's connector terminology and screens for MCP tools have moved around across Copilot Studio releases, so the exact click path may differ from what's described here — search Microsoft's own Copilot Studio / M365 Copilot documentation for "MCP" or "custom connector" if a step doesn't match your tenant's current UI. The destination is always the same: a Streamable HTTP server URL plus a bearer-token header.

Other agents

Any MCP client that supports Streamable HTTP servers with custom headers can connect the same way. Most desktop and editor clients read this shape from an .mcp.json file (or an equivalent settings screen that amounts to the same three fields — URL, transport, header):

{
  "mcpServers": {
    "postnomic": {
      "type": "http",
      "url": "https://mcp.postnomic.com/mcp",
      "headers": { "Authorization": "Bearer pnp_..." }
    }
  }
}

Replace pnp_... with your own token, and consult your client's documentation for where it expects this configuration to live. If your agent's setup screen asks for the pieces individually rather than a JSON block, the three values are still: the URL, "Streamable HTTP" (or just "HTTP") as the transport, and an Authorization: Bearer pnp_... header.

What the agent can do — and can't

No matter which client connects, the Postnomic MCP server is a thin adapter over the same REST API that powers the dashboard — see MCP Server Overview for the full explanation. In practice:

The agent authenticates and acts as you — it inherits your existing blog roles (Admin, Author, etc.) and can't do anything you couldn't already do in the dashboard yourself.
Every tool call still goes through the same quota, role, and subscription checks as the API and dashboard. A Free-tier PAT is rejected outright — MCP access requires a Plus, Pro, or Enterprise plan.
Revoking the PAT from the Access Tokens page immediately disconnects that agent, regardless of which client it's configured in.

Troubleshooting

Connector says "unauthorized" or "access denied." Double-check the header is exactly Authorization: Bearer pnp_... (some UIs split "Bearer" and the token into separate fields — make sure both end up concatenated correctly with a single space). Also confirm the PAT hasn't been revoked and that your account is on a paid plan.
Tools don't appear after adding the server. Some clients require an explicit reconnect or reload of MCP servers after adding or editing one — look for a "reload"/"restart" action in the same settings screen rather than assuming the addition failed.
The client's UI doesn't match these steps. That's expected and not a sign anything is broken on the Postnomic side — agent vendors iterate on their MCP configuration screens frequently. Look for the same three ingredients (URL, Streamable HTTP transport, bearer header) in whatever your client currently calls its MCP/tools/connector settings.

Was this article helpful?

Back to category