Claude 拡張機能設定ツール

What is Claude 拡張機能設定ツール?

Claude 拡張機能設定ツール manages MCP (Model Context Protocol) server configurations for Claude Desktop app and Cursor IDE. It generates settings files from template JSON files and a .env file, then installs them into the appropriate configuration directories. This tool is for users who want to quickly enable or customize MCP integrations.

How to use Claude 拡張機能設定ツール?

Clone the repository, create a .env file with API keys and paths, then run make select-mcps (interactive selection) or make setup for Claude Desktop, or ./scripts/setup_cursor_mcp.sh for Cursor IDE. Restart the application to apply changes.

Key features of Claude 拡張機能設定ツール

• Interactive MCP server selection via make select-mcps
• Supports 11 MCP integrations (Brave Search, filesystem, Git, GitHub, shell, Puppeteer, Fetch, Claude CLI, AWS Documentation, Supabase, Obsidian)
• Works for both Claude Desktop and Cursor IDE
• Uses templates and .env for reproducible, customizable setups
• Includes Obsidian note management tools (write, read, search, delete)

Use cases of Claude 拡張機能設定ツール

• Set up a development environment with GitHub, Git, and shell MCPs
• Enable web scraping via Puppeteer and Brave Search for research
• Integrate with Obsidian vault for note creation and search
• Add AWS Documentation lookup and Supabase database access
• Quickly prototype and test custom MCP servers by adding them to the template

FAQ from Claude 拡張機能設定ツール

What are the prerequisites?

Bun and make must be installed. Claude Desktop or Cursor IDE should be installed. For AWS Documentation, uvx is required.

How do I configure API keys and paths?

Create a .env file in the project root with variables like BRAVE_API_KEY, GITHUB_TOKEN, BUN_PATH, and others as documented. The tool reads this file when generating configuration.

Can I enable only some MCP servers?

Yes. Run make select-mcps for an interactive menu to choose exactly which servers to enable. Alternatively, edit .env and the template files manually.

Where does data live?

Configuration files (claude_desktop_config.json or `config.json) are generated locally and installed into the Claude Desktop or Cursor IDE config directories. No data is sent externally.

How do I troubleshoot setup issues?

Check console output for errors, verify .env paths, ensure bun works, and confirm that OBSIDIAN_VAULT_DIR is set for Obsidian features. If interactive setup fails, try make setup instead.