概览
What is 句碑 API MCP Server?
句碑 API MCP Server is an MCP (Model Context Protocol) server that enables AI agents to query the Haiku Monument Database (句碑データベース). It provides tools for retrieving information about haiku monuments stored in a public GitHub repository. The server is currently in a pre-release beta stage.
How to use 句碑 API MCP Server?
Install with pnpm install, then build with pnpm run build. Configure the server by adding the appropriate entry to your MCP client’s configuration file (e.g., claude_desktop_config.json on macOS or mcp.json for Cursor), pointing to the built dist/index.js file.
Key features of 句碑 API MCP Server
- List all haiku monuments in the database
- Filter monuments by a specified region
- Count monuments by prefecture (Japanese prefecture)
- Query monuments within a given latitude/longitude bounding box
- Retrieve monument data in GeoJSON format
Use cases of 句碑 API MCP Server
- AI assistants answering questions about haiku monument locations
- Mapping applications that display haiku monument data by region
- Educational tools exploring the geographic distribution of haiku inscriptions
- Research projects analyzing haiku monuments across prefectures
- Interactive map generation from monument coordinates and GeoJSON data
FAQ from 句碑 API MCP Server
What does 句碑 API MCP Server do?
It provides a set of MCP tools that let an AI agent access and query a database of haiku monuments. The server runs locally and communicates via the MCP protocol (stdin/stdout transport).
What are the dependencies or runtime requirements?
The server requires Node.js and the pnpm package manager. It has no external authentication or API keys mentioned in the README.
Where does the data come from?
The data is sourced from an external GitHub repository: shikano35/haiku_monument_api. The server fetches from that public database; no local storage is involved.
Is the server stable and ready for production?
No – the README states it is currently a pre‑release (beta). The specification may change in the future as it is still experimental.
What transport and authentication are used?
The server uses the standard MCP stdio transport (command‑line invocation). No authentication mechanism is described in the README.
