Skip to main content

Development

Set up MCP Jupyter for development and contribution.

Development Setup

1. Clone the Repository

mkdir ~/Development
cd ~/Development
git clone https://github.com/block/mcp-jupyter.git
cd mcp-jupyter

2. Create Development Environment

# Sync all dependencies including dev tools
uv sync

3. Run Tests

# Run all tests
uv run pytest tests/

# Run with coverage
uv run pytest --cov=mcp_jupyter tests/

# Run specific test file
uv run pytest tests/test_integration.py

Using Development Version

With Goose

For development, use the local installation:

goose session --with-extension "uv run --directory $(pwd) mcp-jupyter"

This allows you to make changes and test them immediately by restarting Goose.

With Other Clients

Update your MCP configuration to point to your local installation:

{
"mcpServers": {
"jupyter": {
"command": "uv",
"args": ["run", "--directory", "/path/to/mcp-jupyter", "mcp-jupyter"],
"env": {
"TOKEN": "your-token-here"
}
}
}
}

Project Structure

mcp-jupyter/
├── src/
│ └── mcp_jupyter/
│ ├── __init__.py
│ ├── __main__.py # Entry point
│ ├── server.py # MCP server implementation
│ ├── notebook.py # Notebook operations
│ ├── jupyter.py # Jupyter integration
│ ├── state.py # State management
│ └── utils.py # Utilities
├── tests/
│ ├── test_integration.py # Integration tests with real Jupyter server
│ └── test_notebook_paths.py # Unit tests for notebook path handling
├── demos/
│ ├── demo.ipynb
│ └── goose-demo.png
├── docs/ # Documentation site
├── pyproject.toml
└── README.md

Making Changes

Code Style

We use ruff for linting and formatting:

# Format code
uv run ruff format .

# Check linting
uv run ruff check .

# Fix linting issues
uv run ruff check --fix .

Testing Changes

  1. Unit Tests: Test individual functions
  2. Integration Tests: Test with real Jupyter server
  3. Manual Testing: Test with your MCP client

Example test:

def test_notebook_creation():
"""Test creating a new notebook."""
notebook_path = "test_notebook.ipynb"
cells = ["import pandas as pd", "print('Hello, World!')"]

create_new_notebook(notebook_path, cells, server_url, token)

assert check_notebook_exists(notebook_path, server_url, token)

Debugging

Using VS Code

  1. Create .vscode/launch.json:
{
"version": "0.2.0",
"configurations": [
{
"name": "Debug MCP Jupyter",
"type": "python",
"request": "launch",
"module": "mcp_jupyter",
"justMyCode": true,
"env": {
"PYTHONPATH": "${workspaceFolder}",
"TOKEN": "BLOCK"
}
}
]
}
  1. Set breakpoints in the code
  2. Run with F5

Contributing

1. Fork and Branch

git checkout -b feature/your-feature-name

2. Make Changes

  • Follow the code style
  • Add tests for new features
  • Update documentation

3. Test Thoroughly

# Run tests
uv run pytest tests/

# Check formatting
uv run ruff format --check .

# Check types
uv run mypy src/mcp_jupyter

4. Submit PR

  1. Push to your fork
  2. Create pull request
  3. Describe changes clearly
  4. Link any related issues

Next Steps