Scrapbox MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_page_contentB | Fetch content from a Scrapbox page by URL |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.