Notion + GitHub Copilot (VS Code): Complete MCP Integration

Notion is a MCP server that Notion's official hosted MCP server providing secure AI tool access to workspace content including pages, databases, and comments through OAuth authentication..

When integrated with GitHub Copilot (VS Code), you can:

• Search and retrieve live context from Notion workspace based on user access and permissions
• Access and query Notion databases to retrieve structured information
• Read page content and metadata from workspace pages you have access to

This guide provides step-by-step instructions to set up Notion in GitHub Copilot (VS Code), including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Notion will be fully integrated and operational
• You can use Notion tools directly in GitHub Copilot (VS Code)
• All Notion capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• Node.js 18 or higher (for STDIO transport only)
• Active Notion workspace with appropriate access permissions
• MCP client that supports remote servers (HTTP/SSE) or STDIO transport
• Notion account with workspace access
• Supported AI tool with MCP client capabilities
• Permission to connect external applications to workspace
• GitHub Copilot (VS Code) installed and configured
• Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install Notion

Install using npm:

npx -y mcp-remote https://mcp.notion.com/mcp

Verify installation:

Connection verified through OAuth flow in your AI tool

Configuration

Step 2: Configure GitHub Copilot (VS Code)

1. Locate your configuration file:

   • Windows: .vscode\\mcp.json in your project directory
   • macOS: .vscode/mcp.json in your project directory
   • Linux: .vscode/mcp.json in your project directory

2. Add server configuration:

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.notion.com/mcp", "https://mcp.notion.com/mcp"],
      "env": {
        
      }
    }
  }
}

3. Restart GitHub Copilot (VS Code)

Completely quit and restart GitHub Copilot (VS Code) to load the new configuration.

Examples

Once configured, you can use Notion in GitHub Copilot (VS Code):

Create Project Documentation

Generate PRDs, tech specs, or architecture docs by pulling context from existing Notion pages

Ask GitHub Copilot (VS Code): "Create a technical specification for the new authentication system based on our security guidelines in Notion"

Expected Result: AI retrieves security guidelines from Notion workspace and generates comprehensive tech spec

Track Campaign Progress

Monitor and report on campaign status using Notion database data

Ask GitHub Copilot (VS Code): "Give me a summary of all marketing campaigns in progress with their current metrics"

Expected Result: AI queries the campaigns database and provides formatted progress report

Search Meeting Notes

Find specific information across all meeting notes in workspace

Ask GitHub Copilot (VS Code): "What decisions did we make about the API redesign in recent meetings?"

Expected Result: AI searches meeting notes and returns relevant decisions with links to source pages

Generate Release Notes

Build release documentation by aggregating information from multiple Notion pages

Ask GitHub Copilot (VS Code): "Create release notes for version 2.0 using our changelog and feature pages"

Expected Result: AI compiles information from multiple pages into formatted release notes

Task Management

Query and analyze tasks from Notion databases

Ask GitHub Copilot (VS Code): "Show me all overdue tasks assigned to the engineering team"

Expected Result: AI filters and presents overdue engineering tasks with details and links

Testing Your Setup

1. Start a new conversation in GitHub Copilot (VS Code)
2. Ask GitHub Copilot (VS Code) to list available tools
3. Try using Notion functionality

Test prompts:

• "What MCP tools are available?"
• "Use Notion to help with my code"
• "Show me what Notion can do"

Troubleshooting

Common Issues

AI Tool Cannot Connect to Notion MCP

Symptoms: Connection timeout or failed errors, Notion MCP not appearing in tool directory, OAuth flow not starting

Cause: AI tool may not support MCP clients or remote MCP connections

Solution:

• Verify your AI tool supports MCP client functionality
• Check if tool supports remote MCP servers (HTTP/SSE transport)
• For tools without remote support, use STDIO with mcp-remote proxy: npx -y mcp-remote https://mcp.notion.com/mcp
• If tool lacks MCP support entirely, request feature from developers

OAuth Connection Fails

Symptoms: Authorization screen does not appear, Cannot complete OAuth flow, Connection succeeds but no workspace access

Cause: OAuth flow interrupted or workspace permissions issue

Solution:

• Use Notion app Settings > Connections > Notion MCP for easiest setup
• Ensure popup blockers are disabled during OAuth
• Check you have appropriate workspace permissions
• Try disconnecting and reconnecting through Notion app

Cannot Access Specific Pages or Databases

Symptoms: Some content returns not found errors, Searches return incomplete results, Database queries fail or return empty

Cause: Content access based on user permissions - AI tool can only see what you can see

Solution:

• Verify you have access to the pages/databases in Notion app
• Check workspace sharing settings for restricted content
• Ensure pages are not in private sections you cannot access
• Contact workspace admin if you need broader access

STDIO Transport Connection Issues

Symptoms: mcp-remote command fails, Connection drops frequently, Slow response times

Cause: STDIO transport requires mcp-remote proxy for hosted Notion MCP

Solution:

• Prefer Streamable HTTP or SSE transport if your tool supports it
• Ensure Node.js and npx are properly installed for STDIO
• Use config: npx -y mcp-remote https://mcp.notion.com/mcp
• Check network connectivity to mcp.notion.com

Tool Does Not Support Remote MCP Servers

Symptoms: Only local/STDIO servers work in tool, HTTP/SSE connections not available, No option to add remote server URL

Cause: Some MCP clients only support local STDIO servers

Solution:

• Use mcp-remote as proxy to convert HTTP to STDIO
• Configuration: command: npx, args: [-y, mcp-remote, https://mcp.notion.com/mcp]
• Alternative: Use open-source notion-mcp-server for local deployment
• Check tool documentation for remote server support roadmap

MCP Configuration Not Loaded

Symptoms: MCP tools not appearing, Copilot does not recognize MCP server

Cause: Configuration file not in correct location or invalid JSON

Solution:

• Verify .vscode/mcp.json exists in project root directory
• Check JSON syntax is valid (no trailing commas, proper quotes)
• Reload VS Code window after making configuration changes
• Check VS Code Developer Tools (Help > Toggle Developer Tools) for errors

MCP Server Not Starting

Symptoms: Tools listed but not responding, Server connection errors

Cause: Server command path incorrect or dependencies missing

Solution:

• Test the MCP server command independently in terminal
• Verify all server prerequisites are installed
• Check that command path is correct (use absolute paths if needed)
• Ensure required environment variables are set in mcp.json
• Review VS Code Output panel for MCP server error messages

GitHub Copilot Subscription Required

Symptoms: Copilot features grayed out, Unable to access Copilot Chat

Cause: No active GitHub Copilot subscription

Solution:

• Sign up for GitHub Copilot subscription (Individual, Business, or Enterprise)
• Verify subscription is active in GitHub account settings
• Re-authenticate GitHub Copilot in VS Code
• Check that VS Code is using correct GitHub account

VS Code Version Too Old

Symptoms: MCP configuration ignored, No mcp.json recognition

Cause: VS Code version below 1.99 does not have native MCP support

Solution:

• Update VS Code to version 1.99 or later
• Check current version: Help > About
• Download latest version from code.visualstudio.com
• After updating, reload window and verify MCP support

{server_name} Tools Not Working

Symptoms: Server connected but tools fail, Error messages when invoking tools

Cause: Server-specific configuration or authentication issues

Solution:

• Verify all required environment variables for {server_name} are set
• Check {server_name} documentation for specific prerequisites
• Test {server_name} with another MCP client to isolate issue
• Review error messages in VS Code Output panel for specific failures

Notion not appearing in GitHub Copilot (VS Code)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Notion installation
• Restart GitHub Copilot (VS Code)
• Check logs for error messages

Next Steps

Now that Notion is integrated with GitHub Copilot (VS Code):

• Explore all Notion capabilities through GitHub Copilot (VS Code)
• Check out other MCP servers that work with GitHub Copilot (VS Code)
• Join the MCP community for tips and support
• Consider contributing to Notion development

Need Help?

• Search for Notion documentation
• Check the GitHub Copilot (VS Code) MCP guide
• Join the MCP community discussions