-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MCP support #1
Comments
Need to look deeper in MCP and figure out if it is a concern for this lib or something on top of it. |
It's surely something on top on it. The main takeaway from my experience (but limited to |
There was already a mechanism to do that but I made it a bit more explicit in 2.6.4: As in export class Plugin4 extends Plugin {
isEnabled(): boolean {
return true
}
getName(): string {
return 'plugin4'
}
/* this is what is new / important */
isCustomTool(): boolean {
return true
}
getDescription(): string {
return 'Plugin 4'
}
async getTools(): Promise<any|any[]> {
return {
type: 'function',
function: {
name: 'plugin4',
description: 'Plugin 4',
parameters: {
type: 'object',
properties: { },
required: [],
},
},
}
}
} Is that good enough or do you need more than that? |
Thank you, this works perfectly for this use case. |
For information I created this some time ago: https://github.com/nbonamy/nestor. Watch the linked videos if you are interested! |
oh oooh, on it thank you! |
Hi, good project thank you for sharing.
I have been playing with it in test project
I would see a nice improvement in a more integrated way to use MCP to handle tools and prompt. What do you think?
The text was updated successfully, but these errors were encountered: