OSS Cross

Provides an MCP server that exposes code access between projects, enabling AI agents to explore, read, and delegate tasks across repositories.

javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "sweetsrepo-cross-project-mcp": {
      "command": "node",
      "args": [
        "/absolute/path/to/cross-project-mcp-server/dist/index.js",
        "/absolute/path/to/your-oss-repo"
      ]
    }
  }
}

A cross-project MCP server lets AI agents in one repository access and reference implementation details from another repository. It enables seamless collaboration by exposing a controlled set of actions to explore, read, and delegate work across projects while keeping all access sandboxed to the source project path.

How to use

You interact with the MCP server through an MCP client inside your project. First, configure the server as described in the installation section. Once configured, agents can discover the target repository and perform practical actions such as exploring the code structure, reading files, searching code, and understanding symbols. The server also supports a task delegation workflow so agents can request work from the repository owner and receive structured task instructions.

How to install

Prerequisites: Node.js installed on your system. You also need access to the repository where the MCP server will run.

bash
cd cross-project-mcp-server
npm install
npm run build

Additional sections

Configuration and security details are provided below. The server is designed to run alongside your source project and is isolated to the specified project directory. Non-essential directories such as node_modules or .git are automatically excluded from access. Path traversal attempts are blocked to protect your environment.

Discovery and delegation features let you access an agent instruction document from the source repository, enabling the agent to understand when and how to delegate tasks. You can use the following tools to interact with the codebase: read_file, list_directory, search_code, get_file_outline, find_files.

For task delegation, agents can submit tasks by writing a structured Markdown document to .agent/tasks/, list and read tasks to track progress, and respond to requests with implemented changes in the source repository.

Available tools

read_file

Read file contents with optional line ranges to inspect specific sections of a source file.

list_directory

Browse the repository directory structure, with an option to recurse into subfolders.

search_code

Search for patterns or text across the codebase using literal or regex queries.

get_file_outline

Extract a structured outline of functions, classes, and symbols from source files.

find_files

Find files by name patterns using glob matching.

get_agent_instructions

Read the agent instructions file to understand the repository's purpose and delegation rules.

submit_task

Create a new task in the inbox by writing a structured task file under .agent/tasks/.

list_tasks

List tasks in the inbox, filterable by status such as OPEN, IN_PROGRESS, DONE, or BLOCKED.

read_task

Read the full content of a specific task file to understand its requirements.