add enabledTools args

[SugiKent]

Key Changes:

• Added --enabledTools parameter that accepts comma-separated tool names
• Implemented tool filtering functionality in filterTools()
• Added comprehensive test coverage for the new feature
• Updated README with usage examples and documentation
• Specifically documented read-only tools for security-conscious implementations

Benefits:

• Allows users to run the server with only necessary tools enabled
• Improves security by limiting exposed functionality
• Reduces attack surface when only read-only access is needed
• Maintains full backward compatibility (all tools enabled by default)

It is particularly important for me as a Cursor user whose number of mcp tools is limited.

Example Usage:

Run with only read-only tools

node build/index.js --enabledTools=notion_retrieve_block,notion_retrieve_page,notion_query_database

Or with specific write tools

node build/index.js --enabledTools=notion_append_block_children,notion_update_page_properties

[suekou]

@SugiKent Thank you for your contribution🚀 !! (コントリビュートありがとうございます)

[agladky]

Hi @suekou! 👋

It's a great update!

However, I noticed that the code uses yargs, but it’s only listed under devDependencies in package.json. As a result, it doesn’t get installed when used via config like this:

"notion": {
  "command": "npx",
  "args": ["-y", "@suekou/mcp-notion-server"],
  "env": {
    "NOTION_API_TOKEN": "key"
  }
}

Here’s the log output:

[notion] [info] Message from client: {"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"claude-ai","version":"0.1.0"}},"jsonrpc":"2.0","id":0}
node:internal/modules/package_json_reader:267
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'yargs' imported from /Users/username/.npm/_npx/be62e5118b20154c/node_modules/@suekou/mcp-notion-server/build/index.js
...

Could you please move yargs to dependencies so it’s available at runtime? Thanks! 🙏

[suekou]

@agladky Thanks for pointing that out! You're right — I've moved yargs to dependencies so it works properly with npx. (#41) Appreciate the heads-up 🙏
I've confirmed it's working in my environment, but could you let me know if it works on your end as well?