mcp-perplexity

This MCP server implements a simple notes system as a TypeScript-based MCP server. It exposes a resource model for notes that are accessed via note:// URIs, and it provides a tool called create_note to add new text notes with a title and content. A prompt named summarize_notes is available to generate a summary of all stored notes, including the notes themselves as embedded resources, suitable for guiding an LLM in producing a concise overview. To run locally, build the TypeScript project and start the server; once running, MCP clients can invoke create_note to persist notes and request summarize_notes to obtain a structured prompt for summarization. The notes are plain text with metadata such as title to help organization and retrieval.

Prerequisites:

• Node.js (LTS recommended) and npm installed on your system
• Basic familiarity with MCP workflow (resources, tools, prompts)

Steps:

1. Install dependencies npm install

2. Build the server npm run build

3. (Optional for development) Enable auto-rebuild on file changes npm run watch

4. Run the server (after build completes) node build/index.js

5. Integrate with clients

   • Use the MCP protocol to connect to the server's stdio interface or configured IO mechanism as per your environment.
   • Call the create_note tool with a title and content to add notes, and use summarize_notes to generate a summary prompt for an LLM.

Tips:

• The server stores notes in memory/state; restart will clear notes unless persistent storage is added in your environment. Consider wiring a persistence layer if needed.
• Debugging MCP interactions is done via stdio. You can use the MCP Inspector tool for a graphical debugging experience: npm run inspector.
• Double-check the build output path (build/index.js) when configuring external runners or editors that load the MCP server.
• If you plan to run this alongside Claude Desktop, ensure the config JSON points to the correct path to the built server (as shown in the installation example).
• Environment variables are optional for basic usage; add them under env in mcp_config if you introduce persistence, authentication, or logging.