GitHub Copilot Integration

PostQuickAI for GitHub Copilot

Copilot reads AGENTS.md and supports MCP in agent mode. Drop our snippet + register the MCP server and Copilot knows how to schedule, generate, and analyze social media without leaving your IDE.

1. Register the MCP server (VS Code)

Create .vscode/mcp.json in your repo:

{
  "servers": {
    "postquickai": {
      "command": "npx",
      "args": ["-y", "@postquickai/mcp"],
      "env": {
        "POSTQUICKAI_API_KEY": "${env:POSTQUICKAI_API_KEY}"
      }
    }
  }
}

Export POSTQUICKAI_API_KEY in your shell so the config can reference it safely (the JSON is committed; the key is not). Commit .vscode/mcp.json so your team shares the same server definition.

2. Drop AGENTS.md at the repo root

Create or open AGENTS.md at your repo root and paste the PostQuickAI section from /agents-md. Copilot reads AGENTS.md automatically — no other config.

Already using .github/copilot-instructions.md? Paste the same snippet there instead — Copilot honors both.

3. Enable agent mode in Copilot Chat

Open the Copilot Chat sidebar in VS Code → click the mode dropdown → choose Agent. MCP tools only appear in agent mode (not Ask or Edit mode).

4. Try it in Copilot Chat

In agent mode:

"Plan this week's social content for our brand — 5 posts spread across weekdays"
"Schedule a launch-day thread for next Tuesday, post to twitter_x and threads at 9am ET"
"Pull last 30 days of analytics and tell me which format performed best"
"Reset and retry any posts that failed yesterday"

API + Agent access

MCP server, Skills, and REST API are all included with the API add-on on any paid plan.

FAQ

Frequently Asked Questions

Yes — Copilot Chat in VS Code (agent mode) now supports MCP servers. Add PostQuickAI to the `github.copilot.advanced.mcp.servers` setting or to `.vscode/mcp.json` in your repo.

AGENTS.md is the universal project-instructions file that Copilot reads automatically. Our snippet tells Copilot when to use the MCP tools, how to handle rate limits, and which skills map to which user phrases. Drop it in your repo root.

MCP is the plumbing (the tools); AGENTS.md is the playbook (when to call them). You can use MCP without AGENTS.md, but you'll get dramatically better Copilot behavior if you have both.

Copilot also reads .github/copilot-instructions.md. If you already have one, paste the PostQuickAI section there. If not, use AGENTS.md — it's the cross-agent standard and Copilot reads it too.

MCP support is most mature in VS Code agent mode today. JetBrains and Visual Studio are adding it progressively. For any Copilot surface that doesn't support MCP yet, AGENTS.md still helps — Copilot can fall back to direct REST calls using the OpenAPI spec.

Troubleshooting

"Failed to connect to postquickai"

Almost always a config format issue. Make sure command is just npx and args is an array — never put the whole command in one string. Also fully quit and restart your agent after editing config.

"API add-on required" / 403 errors

MCP and REST API access both require the API add-on on your plan. Enable it at postquick.ai/pricing.

"Missing POSTQUICKAI_API_KEY"

Generate a key at postquick.ai/dashboard/api. Keys start with pq_live_. Put it in the env block of your MCP config.

Rate limit exceeded

Basic plan: 30 req/min, 5k/day. Pro plan: 120 req/min, 50k/day. See rate limits in the API docs.

GitHub Copilot-specific issues

Still stuck? See the developer docs or email support@postquick.ai.

Also works with

PostQuickAI is agent-native — same API, same MCP server, same skills bundle across every major AI coding agent.

Ship code + ship posts — same IDE, same agent

Copilot already writes your PRs. Now it can run your social calendar too.

Start free trial