mcp-tavily

The tavily-server MCP implementation provides a simple notes system as an MCP server. It exposes a text-note resource model where each note is accessible via note:// URIs and includes a title, content, and metadata. Two built-in tools are available: create_note, which accepts a title and content to create a new note stored in the server state, and summarize_notes, a prompt that generates a summary of all stored notes and returns a structured prompt suitable for an LLM to perform summarization. You can interact with these capabilities through MCP clients that send the defined commands and prompts via the MCP protocol. When running, you can start the server and then issue create_note with the required parameters to populate notes, then call summarize_notes to obtain an aggregated summary along with embedded note resources.

Prerequisites:

• Node.js (LTS version) and npm installed
• Basic familiarity with running Node-based MCP servers

Steps:

1. Install dependencies

   • Run: npm install

2. Build the TypeScript server

   • Run: npm run build

3. (Optional) Enable development with auto-rebuild

   • Run: npm run watch

4. Run the server

   • Ensure you have Node.js installed and the build artifacts present (build/index.js)
   • Start the server (the exact start command may depend on your environment):
     • node build/index.js

5. Configure clients

   • Use the provided MCP config format (see mcp_config) to register the server with your MCP client or Claude Desktop integration. Ensure the path to the built index.js is correct for your environment.

Notes:

• The server uses note:// URIs for accessing notes and serves plain text content for simple interactions.
• The create_note tool requires title and content as parameters.
• The summarize_notes prompt aggregates all notes and returns a structured prompt for LLM-assisted summarization.
• Debugging MCP servers is often done using the MCP Inspector tool. You can invoke the inspector via npm run inspector.
• When integrating with Claude Desktop, place the server configuration in the appropriate claude_desktop_config.json file as described in the README.
• If you customize paths, ensure the server is started with the same working directory from which the build/index.js path is valid.