Search Fetch Server MCP

🚀 Search Fetch Server MCP Server

A TypeScript-based MCP server implementing a simple note system. This example demonstrates core MCP concepts, including:

• Resources: Text notes with metadata are represented using note:// URIs.
• Tools: Used to create new notes, fetch URLs, and perform searches.
• Prompts: Generate summaries of all stored notes.

✨ Features

Resources

• List and access notes with note:// URIs.
• Each note contains a title, content, and metadata.
• Use the plain text mime type for simple content access.

Tools

• create_note: Create a new text note.
  • Title and content parameters are required.
  • Store the note in the server state.
• fetch_url: Fetch content from a URL, optionally convert it to Markdown using Puppeteer.
  • A URL parameter is required.
  • An optional boolean parameter use_puppeteer can be provided. If set to true, use Puppeteer with waitUntil set to networkidle2 and a 30-second timeout. Otherwise, use axios to fetch the content.
  • Return the Markdown content of the URL if Puppeteer is used, otherwise return the content as is.
• duckduckgo_search: Perform a DuckDuckGo search.
  • A query parameter is required.
  • Return the search results as a JSON string.

Prompts

• summarize_notes: Generate a summary of all stored notes.
  • Include all note content as embedded resources.
  • Return a structured prompt for an LLM to summarize.

📦 Installation

Development

Install dependencies:

npm install

Build the server:

npm run build

Develop with automatic rebuild:

npm run watch

Usage in Claude Desktop

To use in Claude Desktop, add the server configuration:

• On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• On Windows: %APPDATA%/Claude/claude_desktop_config.json

Add the following content to the configuration file:

{
  "mcpServers": {
    "search-fetch-server": {
      "command": "node",
      "args": ["/path/to/search-fetch-server/build/index.js"]
    }
  }
}

Debugging

Since MCP servers communicate via stdio, debugging can be challenging. We recommend using MCP Inspector, which can be run via an npm script:

npm run inspector

The Inspector will provide a URL to access the debugging tool in the browser.