Scotland's data,
in any MCP client

A remote MCP server at https://mcp.scotfact.com that gives your AI client three things:

• The Holyrood Official Report — every speech and contribution made in the Scottish Parliament chamber since 1999, refreshed daily.
• Scottish economic and fiscal datasets — GERS, QNAS, ONS Pink Book, ONS UK GDP, Export Statistics Scotland, oil and gas revenue and the Scottish Budget — all sourced from the underlying official publications and exposed as queryable data.
• The GERS methodology papers — the "Detailed Methodology" documents explaining how each revenue and expenditure line in GERS is estimated and apportioned to Scotland, covering every published year from 2006-07 to 2023-24. This is the how behind the numbers, searchable line item by line item and year by year.

The server is free, public and read-only. There's no account to create and no API key to manage. You will need to authenticate with a Google or Microsoft account to access it (more social sign-in options are coming), but Scotfact does not process the authentication itself.

It's a standard remote MCP server speaking Streamable HTTP, so it is not tied to any one assistant — anything that can add a remote MCP server can use it. The setup steps below are written out in full for Claude, with ChatGPT and other clients covered after them.

You'll need:

• An assistant that can add a remote MCP server. On Claude that means a plan supporting custom connectors — as of writing, Free (limited to one custom connector), Pro, Max, Team and Enterprise. On ChatGPT it means a plan where connectors are available to you.
• About two minutes.

1. Go to Settings → Connectors (or click the + button next to "Connectors" if you see it in the sidebar).
2. Click Add custom connector.
3. Enter a Name — Scotfact, or anything you like; it's just the label Claude shows you — and the URL https://mcp.scotfact.com.
4. Leave the advanced OAuth fields blank. Scotfact doesn't require static authentication ids.
5. Click Add.

That's it. The connector should show as connected, and the Scotfact tools will be available in your next conversation.

Custom connectors are configured once in your Claude account and are then available everywhere — Claude Desktop, the iOS and Android apps, and Cowork all pick up the same connector list. Nothing needs installing separately on each device.

If you've already added Scotfact via claude.ai, it will appear automatically in Claude Desktop and the mobile apps next time you sign in. No authorization_token is needed — Scotfact is open.

Nothing about Scotfact is Claude-specific. It is a remote MCP server over Streamable HTTP with OAuth sign-in, so any client that speaks MCP can connect to the same URL:

https://mcp.scotfact.com

ChatGPT

Add Scotfact as a connector from ChatGPT's settings, using the URL above. Where connectors live in the interface, and which plans and modes expose them, has moved around more than once — so follow OpenAI's current documentation for adding a remote MCP server rather than a fixed set of menu clicks here. No client id or secret is needed; you'll be taken through the same Google or Microsoft sign-in.

Everything else

• Claude Code — claude mcp add --transport http scotfact https://mcp.scotfact.com
• IDE and editor integrations that support remote MCP servers — add the URL as an HTTP/streamable server.
• Your own MCP host — point any Model Context Protocol client at the URL and complete the OAuth flow.

By default, custom connectors are available but not always actively in use in every conversation. On claude.ai and the mobile apps, click the + button at the bottom-left of the chat input, choose Connectors, and toggle Scotfact on for that conversation. You only need to do this once per conversation.

Most other clients work the same way — the connector is registered once at the account or config level, then switched on per conversation. If your assistant isn't reaching for Scotfact, that toggle is the first thing to check.

Try one of these prompts in a conversation where Scotfact is enabled, whichever client you're using:

• "What did Nicola Sturgeon last say about an independence referendum?"
• "What was the most recent vote in the Scottish Parliament?"
• "How does Scotland's revenue per head compare to the UK over the last ten years?"
• "What's in the GERS dataset?"
• "How does GERS estimate Scotland's share of Corporation Tax?"

Your assistant will call Scotfact's tools and answer with figures and quotes drawn directly from the source. Citations appear inline as links back to the relevant page on apps.scotfact.com or scotfact.com, so you can check any quote or figure against the published view.

The server exposes three separate worlds.

They don't talk to each other automatically. For cross-cutting questions — "summarise the Stage 3 budget debate, check the figures being argued over against GERS, and explain how that line is estimated" — just ask your assistant to use all three and it will combine them.

Scotfact serves only public information — Hansard-equivalent parliamentary speeches and published Scottish Government, ONS and HMRC statistics. There is no user account, no login and no personal data collected by the server. Your prompts remain subject to your provider's privacy policy as normal — Anthropic's for Claude, OpenAI's for ChatGPT, and so on. Scotfact only sees the queries the assistant itself constructs (for example, "search Holyrood for Sturgeon contributions about referendum").

Third-party connectors are unverified by definition. Claude, ChatGPT and others all show a generic warning when you add one — that's not something specific to Scotfact.

On claude.ai: Settings → Connectors, find Scotfact, then Remove. On Claude Code: claude mcp remove scotfact. In ChatGPT and other clients, remove it from wherever you added it — the connector list in settings.

That's all there is to it. The data does the rest.