Scrapbox MCP Server
# scrapbox-mcp MCP Server
A Model Context Protocol server
This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:
- Resources representing text notes with URIs and metadata
- Tools for creating new notes
- Prompts for generating summaries of notes
## Features
### Resources
- List and access notes via `note://` URIs
- Each note has a title, content and metadata
- Plain text mime type for simple content access
### Tools
- `create_note` - Create new text notes
- Takes title and content as required parameters
- Stores note in server state
### Prompts
- `summarize_notes` - Generate a summary of all stored notes
- Includes all note contents as embedded resources
- Returns structured prompt for LLM summarization
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## Installation
To use with Claude Desktop, add the server config:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"scrapbox-mcp": {
"command": "/path/to/scrapbox-mcp/build/index.js"
}
}
}
```
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The tool's purpose is clearly defined and distinct by default.
The single tool follows a clear verb_noun pattern (get_page_content), and with no other tools to compare, consistency is inherently perfect. There are no deviations or mixed conventions.
One tool is too few for a server named 'Scrapbox MCP Server', which implies broader functionality for interacting with Scrapbox pages. A single fetch tool feels thin and limited in scope, suggesting an incomplete or minimal implementation.
The tool surface is severely incomplete for a Scrapbox server, covering only fetching page content. Obvious gaps include creating, updating, deleting, or listing pages, which are essential operations for managing a wiki or note-taking system like Scrapbox.