mcpField
M
mcp-client-and-server MCP server

mcp-client-and-server MCP server

Local
github.com/non-dirtyDeveloper Tools2Updated 99w ago

About mcp-client-and-server MCP server

mcp-client-and-server MCP server is a small note-storage MCP server intended for chaining clients and servers. It provides note resources, an add-note tool, and a prompt that summarizes stored notes with an optional detail style.

Key features

  1. 01Store notes as named resources
  2. 02Access notes through note:// URIs
  3. 03Add notes with a tool
  4. 04Summarize stored notes with a prompt
  5. 05Set brief or detailed summary style

Use cases

  1. 01Save notes through an MCP client
  2. 02Retrieve an individual stored note
  3. 03Generate a summary of stored notes
  4. 04Choose a brief or detailed summary

MCP support

Implements an MCP server with note resources, an `add-note` tool, and a `summarize-notes` prompt. The project description also identifies it as a client and server for chaining clients and servers.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

mcp-client-and-server MCP server

Model Context Protocol Client and Server to chain together between clients and servers

Components

Resources

The server implements a simple note storage system with:

  • Custom note:// URI scheme for accessing individual notes
  • Each note resource has a name, description and text/plain mimetype
Prompts

The server provides a single prompt:

  • summarize-notes: Creates summaries of all stored notes
    • Optional "style" argument to control detail level (brief/detailed)
    • Generates prompt combining all current notes with style preference
Tools

The server implements one tool:

  • add-note: Adds a new note to the server
    • Takes "name" and "content" as required string arguments
    • Updates server state and notifies clients of resource changes

Configuration

[TODO: Add configuration details specific to your implementation]

Quickstart

Install
Claude Desktop

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

Development/Unpublished Servers Configuration ``` "mcpServers": { "mcp-client-and-server": { "command": "uv", "args": [ "--directory", "/Users/mlrsmith/Library/Mobile Documents/com~apple~CloudDocs/Family_Shared/AI/mcp/mcp-client-and-server", "run", "mcp-client-and-server" ] } } ```
Published Servers Configuration ``` "mcpServers": { "mcp-client-and-server": { "command": "uvx", "args": [ "mcp-client-and-server" ] } } ```

Development

Building and Publishing

To prepare the package for distribution:

  1. Sync dependencies and update lockfile:
uv sync
  1. Build package distributions:
uv build

This will create source and wheel distributions in the dist/ directory.

  1. Publish to PyPI:
uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: --token or UV_PUBLISH_TOKEN
  • Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD
Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /Users/mlrsmith/Library/Mobile Documents/com~apple~CloudDocs/Family_Shared/AI/mcp/mcp-client-and-server run mcp-client-and-server

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.