Supernotes to Obsidian MCP server

Automates importing Supernotes exports into Obsidian daily notes, formatting content and adding wikilinks for seamless note migration.
Back to servers
Setup instructions
Provider
Alex Howard
Release date
Dec 29, 2024
Language
Python

This Python script serves as a bridge between Supernotes exports and Obsidian daily notes using the Model Context Protocol (MCP). It automatically imports your Supernote content into Obsidian, creates daily notes when needed, and enhances your notes with proper formatting and wikilinks.

Installation

To set up the Supernotes to Obsidian converter:

  1. Create and activate a virtual environment:
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
  1. Install the required MCP dependency:
uv add mcp

Configuration

Before running the script, you need to configure your settings in the config.py file:

TEMPLATE_PATH = '/path/to/your/template.md'
EXPORT_FOLDER = '/path/to/supernote/exports'
DAILY_NOTES_FOLDER = 'Daily Notes'

Configuration Options

  • TEMPLATE_PATH: Path to your Obsidian daily note template
  • EXPORT_FOLDER: Directory containing your Supernotes exports
  • DAILY_NOTES_FOLDER: Destination folder for Obsidian daily notes

Usage

Once configured, run the script with:

python src/main.py

What It Does

When executed, the script will:

  • Scan your Supernotes export folder
  • Create Obsidian daily notes using your template if they don't exist
  • Import and format your Supernotes content
  • Clean up formatting issues
  • Add wikilinks for proper nouns
  • Handle OCR errors automatically

For best results, organize your Supernotes exports in a dedicated folder and ensure your Obsidian vault is properly set up with a daily notes template.

How to install this MCP server

For Claude Code

To add this MCP server to Claude Code, run this command in your terminal:

claude mcp add-json "supernotes-to-obsidian" '{"command":"python","args":["src/main.py"]}'

See the official Claude Code MCP documentation for more details.

For Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "supernotes-to-obsidian": {
            "command": "python",
            "args": [
                "src/main.py"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.

For Claude Desktop

To add this MCP server to Claude Desktop:

1. Find your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

2. Add this to your configuration file:

{
    "mcpServers": {
        "supernotes-to-obsidian": {
            "command": "python",
            "args": [
                "src/main.py"
            ]
        }
    }
}

3. Restart Claude Desktop for the changes to take effect

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later