How should cross plugin dependencies be handled?

Open
#313 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the community-plugins repository and the dependency-related behavior described for bn-ebpf-solana. Compare its MCP client integration with the linked binary_ninja_mcp plugin, then determine what dependency declaration or installation behavior would need to be supported and how completion could be verified.

Written by the indexing model from the issue text.

Description

Hi, I maintain bn-ebpf-solana and having recently integrated an MCP client into the plugin, it now relies on this MCP server plugin being installed.

Is there a builtin way to specify this constraint?

Dominant language
Python
Stars
589
Forks
50
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/community-plugins

All issues in Vector35/community-plugins

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.