What is jupyter-collaboration-mcp AGENTS.md?

Project instructions for a JupyterLab extension that provides MCP server endpoints for real-time collaboration in Jupyter notebooks and documents. MCP is a communication standard that lets AI agents interact with tools and data.

It is for working on the Jupyter Collaboration MCP Server, including its real-time collaboration features and YDoc-based conflict-free synchronisation.

It explains the project’s structure and its notebook-synchronisation concepts, helping an agent contribute without misunderstanding how shared edits work.

How complyue/jupyter-collaboration-mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to complyue/jupyter-collaboration-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/complyue/jupyter-collaboration-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/complyue/jupyter-collaboration-mcp

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/complyue/jupyter-collaboration-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/complyue/jupyter-collaboration-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/complyue/jupyter-collaboration-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/complyue/jupyter-collaboration-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/complyue/jupyter-collaboration-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/complyue/jupyter-collaboration-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,965 This file is loaded in full into every session.

When invoked 1,965 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01965	$0.01965
Opus 5.5	$0.00786	$0.00786
Sonnet 5.5	$0.00393	$0.00393
Haiku 4.5	$0.00197	$0.00197

Measured 2mo ago against content hash 6d34b1b722e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jupyter-collaboration-mcp AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

AGENTS.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Agent Guide for Jupyter Collaboration MCP Server

This guide provides AI agents with the essential information needed to understand, contribute to, and work effectively with the Jupyter Collaboration MCP Server project.

Project Overview

The Jupyter Collaboration MCP Server is a JupyterLab extension that provides MCP (Model Context Protocol) server endpoints to expose Jupyter Collaboration's real-time collaboration (RTC) functionalities to AI agents. This project enables AI agents to interact with collaborative Jupyter notebooks and documents in real-time, leveraging the existing Jupyter Collaboration system's robust RTC capabilities using YDoc (CRDT) technology.

Key Concepts for AI Agents

MCP (Model Context Protocol): The communication standard between AI agents and the server
RTC (Real-Time Collaboration): The underlying technology enabling multiple users to collaborate simultaneously
YDoc: CRDT (Conflict-free Replicated Data Type) technology used for synchronization
Jupyter Collaboration: The existing system providing collaborative features for Jupyter notebooks

Project Structure

Based on the design document, the project follows this structure:

jupyter-collaboration-mcp/
├── pyproject.toml
├── setup.py
├── jupyter_collaboration_mcp/
│   ├── __init__.py
│   ├── app.py              # Main MCP server application
│   ├── handlers.py         # MCP request handlers
│   ├── rtc_adapter.py      # Adapter to existing RTC functionality
│   ├── event_store.py     # For resumability
│   ├── auth.py            # Authentication and authorization
│   └── utils.py           # Utility functions
└── tests/
    ├── __init__.py
    ├── test_app.py
    ├── test_handlers.py
    └── test_auth.py

Key Components

1. MCP Server (StreamableHTTP)

Located in app.py
Uses HTTP with Server-Sent Events (SSE) for real-time communication
Based on the MCP StreamableHTTP example

2. RTC Adapter Layer

Located in rtc_adapter.py
Translates MCP requests into operations on the existing collaboration system
Bridges the gap between MCP protocol and Jupyter Collaboration

Read the full file on GitHub · 261 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 261 lines · 1,965 tokens per session scan A 6d34b1b722e9

Subscribe to this mod's changes

jupyter-collaboration-mcp AGENTS.md is an instructions file published in the GitHub repository complyue/jupyter-collaboration-mcp (0 stars, last pushed 1y ago), licensed MIT. It adds 1,965 tokens to every session, about $0.0079 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

jupyter-collaboration-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
jupyter-collaboration-mcp AGENTS.mdcomplyue/jupyter-collaboration-mcp	Instructions file	0	1y ago	MIT	A	1,965	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

jupyter-collaboration-mcp: Instructions file for Codex