VS Code MCP server for GitHub Copilot

How it works

GitHub Copilot in VS Code can call MCP servers in agent mode. Add blogr once and Copilot can look up your articles, topical map and Search Console numbers while it works in your repository. VS Code handles the sign-in itself: it finds blogr's OAuth server, registers, and opens the consent screen in your browser.

Copilot acts as you, with your team role on each website, and can change only what your role allows.

What you need

A blogr account. Each website's data is available while its owner has an active plan or trial.
VS Code with GitHub Copilot. On Copilot Business and Enterprise, your organization must allow MCP servers.

Connect VS Code

Open the Command Palette and run MCP: Add Server.
Choose HTTP, paste this URL, and name the server blogr:

https://blogr.ai/mcp

Allow VS Code to sign in when it asks. blogr opens in your browser, where you choose Allow access.
Open Copilot Chat in Agent mode and ask "Using blogr, list my websites."

To share the setup with your team, commit it as .vscode/mcp.json. Each person signs in with their own blogr account:

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

Things to ask Copilot

"List the blogr articles published this month and add them to our changelog page."
"Which topical map pages are still missing from this site? Open an issue for each."
"Show my top ten queries by clicks for the last 28 days."
"Approve the waiting titles about pricing and schedule them for next week."

What Copilot can do

Copilot reads without asking. Every tool that changes something is marked as a write, so Copilot asks you to confirm before it runs.

Tool	What it does	Changes data
list_websites	Your websites, your role on each, and whether each has a plan, a topical map and Search Console.	No
get_website_overview	Article counts by status, what is scheduled next, failures, map coverage and the monthly allowance left.	No
list_articles	Articles by status, with dates and live links.	No
get_article	One article in full: the Markdown body, SEO title, meta description, categories and tags.	No
get_topical_map	The map by silo, then each page with its query, search volume, difficulty and current rank.	No
get_performance	Search Console clicks, impressions, CTR and position for 7, 28 or 90 days, with top queries and pages.	No
get_article_impact	How recent articles are moving in Google week over week.	No
list_opportunities	The SEO opportunities blogr found in your Search Console data.	No
get_usage	Your plan and this month's article allowance.	No
approve_titles	Approves titles onto your publishing schedule, one per slot, the same as the approval tray.	Yes
decline_titles	Declines titles that are not written yet. You can approve them again later.	Yes
add_article_idea	Adds your own title on the next open slot, like Add title in the app.	Yes
reschedule_article	Moves a scheduled article to another day and pins it there.	Yes
update_article	Renames a title, or edits a written draft's title, body, SEO fields, categories and tags.	Yes

What Copilot cannot do

Publish, delete or archive articles. Publishing stays in blogr, so nothing reaches your live site from Copilot.
Start writing an article early. Approved titles are written on their scheduled day, within your monthly allowance.
See or change billing, website settings, team members, or your publishing connection and its tokens.

An edit to a published article is saved in blogr. The live page changes the next time you publish that article from blogr.

Team roles

Copilot follows your role on each website. Viewers can read everything they see in the app, and Copilot cannot change anything for them. Editors and admins can approve, decline, add, reschedule and edit through Copilot. Owners can do all of it.

Limits

120 requests per minute per account, across every assistant you connect.
200 changes per account per hour.
25 titles added through an assistant per website per day.

Past a limit, Copilot gets a message saying so and can try again later. Nothing you do in the app counts toward these limits.

Your data

Copilot receives only what you ask for: your websites, articles, topical map, Search Console performance and opportunities.
blogr never sees your Copilot conversations. For each request it records which tool ran, on which website, whether it worked and how long it took, and deletes that record after 90 days.
Copilot signs in with its own access token, which never includes your password. To disconnect, run MCP: List Servers in VS Code and remove blogr, then sign blogr out under Accounts.

Once Copilot receives data from blogr, GitHub Copilot handles it under its privacy policy. Read blogr's own privacy policy for what we store.

Troubleshooting

Copilot never calls blogr: MCP tools only run in Agent mode. Check blogr is ticked in the tools picker.
MCP: Add Server is missing: your organization may have switched MCP off in Copilot policies.
"blogr needs an active plan or trial": start a plan or trial on the account that owns the website.
"Your role does not allow this": ask the website owner to give you the Editor or Admin role.

Questions

Does blogr work with GitHub Copilot?

Yes. Add https://blogr.ai/mcp as an HTTP MCP server in VS Code and use it from Copilot agent mode.

Can my whole team use the same setup?

Yes. Commit .vscode/mcp.json to the repository. Each person signs in to blogr with their own account and gets their own role.

Can Copilot publish articles?

No. Copilot can approve, decline, add, reschedule and edit articles. Publishing stays in blogr.