Reduce the number of Appwrite MCP tool

Cursor has 40 MCP tools limit to use, but Appwrite solely has 195 tools, so it cannot be used with other tools nor handling multiple Appwrite MCP tools. Is there any plan to reduce(integrate) the number of tools so that can be harmonized with other MCP tools?

[REQUEST] Reduce the number of Appwrite MCP tool

You can pass some flags to only enable some tools. See https://github.com/appwrite/mcp/tree/main#command-line-arguments

Reduce the number of Appwrite MCP tool

Even though I only give --databases parameter, still exceeds Cursor's 40 limit

That's too bad. Databases service has a lot of endpoints

I deleted photo due to reveal of API key, anyway it should be condensed somehow

Windsurf accepts more than 40

But I've already paid for annual subscription 🥹

Ooh, I think this error was because of the free trial. Haha, you saved my day, I was just about to subscribe!

@Steven @Chirag Aggarwal I know I may not mention directly, but is there any ongoing discussion for this issue? This still hinders from using with other MCP tools. Compared to Supabase which has approximately 32 tools, Appwrite has too much seperate tools.

I would suggest adding a 👍🏼 to https://github.com/appwrite/mcp-for-api/issues/17

Actually, that's the issue that I wrote 🙁

And it's almost 1 year past by, but still no news

i would love to work closely with you on this

do you have a list of tools you use more often? idea is we have a way smaller selection of enabled tools by default and allow users to configure them more in more granularity

Alright, that's a good start.

But I want to ask a fundamental question: "Why the tools are all seperated with each types?" Like tables_db_create_datetime_column, tables_db_create_email_column, etc...

How about just integerate them, and let user or AI select the type? For example, make tables_db_create_column(integrated), and user/AI send a request with the type they want.

Is there any hinderance to acheive it? I'm not the expert in this area, so tell me if it's technically impossible.

It mirrors our endpoints. A lot of our stuff is build around the open API specs of our endpoints

This helps us better maintain everything