Notion + Amazon Q CLI: 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 Amazon Q CLI, 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 Amazon Q CLI, 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 Amazon Q CLI
- 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
- Amazon Q CLI 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 Amazon Q CLI
- Install Amazon Q CLI
Download and install Q CLI for your platform
Visit: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html
- Authenticate
Set up authentication with AWS Builder ID or IAM Identity Center
q auth
Note: Follow interactive authentication flow
- Verify Installation
Test Q CLI installation and configuration
q doctor
- Install MCP Server
Install the MCP server you want to integrate
Note: Ensure server is accessible from command line
- Configure MCP Integration
Add MCP server configuration to Q CLI
Note: Use q config commands to set server parameters
- Test Integration
Verify MCP server works with Q CLI
q chat "Use Notion to help me"
Configuration Details
Configure MCP servers through Q CLI commands:
# Configure MCP server integration
q config set mcp.servers.notion.command "npx"
q config set mcp.servers.notion.args ""-y", "mcp-remote", "https://mcp.notion.com/mcp", "https://mcp.notion.com/mcp""
q config set mcp.servers.notion.env ""
# Verify configuration
q config list mcp.servers
Examples
Once configured, you can use Notion in Amazon Q CLI:
Create Project Documentation
Generate PRDs, tech specs, or architecture docs by pulling context from existing Notion pages
Ask Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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
- Run q doctor to verify system health
- Start Q CLI chat session
- Ask Q to list available MCP tools
- Test specific Notion functionality
Test commands:
q doctor
q chat
q config list mcp.servers
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
Installation Failed
Symptoms: Q command not found, Installation errors
Cause: Incomplete installation or PATH issues
Solution:
- Verify installer completed successfully
- Check PATH environment variable includes Q CLI
- Try running q doctor for diagnostics
- Reinstall using platform-specific method
Authentication Problems
Symptoms: Auth errors, Cannot connect to AWS services
Cause: Invalid credentials or network issues
Solution:
- Run q auth to re-authenticate
- Verify AWS Builder ID or IAM credentials
- Check network connectivity to AWS
- Ensure proper AWS permissions are set
MCP Server Not Found
Symptoms: Server command not found, MCP tools unavailable
Cause: Server not installed or not in PATH
Solution:
- Verify MCP server installation
- Check server executable permissions
- Use absolute path in configuration
- Test server independently with direct command
Configuration Errors
Symptoms: Config commands fail, Settings not persisting
Cause: Invalid configuration syntax or permissions
Solution:
- Check Q CLI configuration file permissions
- Verify configuration syntax is correct
- Use q config list to review current settings
- Report issues with q issue command
Notion not appearing in Amazon Q CLI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Notion installation
- Restart Amazon Q CLI
- Check logs for error messages
Next Steps
Now that Notion is integrated with Amazon Q CLI:
- Explore all Notion capabilities through Amazon Q CLI
- Check out other MCP servers that work with Amazon Q CLI
- Join the MCP community for tips and support
- Consider contributing to Notion development
Need Help?
- Search for Notion documentation
- Check the Amazon Q CLI MCP guide
- Join the MCP community discussions