Support for custom (user-defined) MCP tools

Open
#8,377 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
api

Research direction

Start by reviewing the repository's public API and examples to understand how built-in MCP tools are exposed. Determine the scope of an API for defining user-provided tools alongside them, including the expected registration and usage model. Done means the proposed capability is implemented and documented with an example.

Written by the indexing model from the issue text.

Description

What is the feature you'd like to have?
Would be awesome to have some kind of API to define user-defined MCP tools alongside with built-in ones.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.