Used for managing environment variables that store Kintone credentials and configuration.
Recommended for cloning and managing the project repository.
Used for managing project dependencies and running build scripts.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Kintone Book Management MCP Tool get information about books by Stephen King"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
このプロジェクトは、Model Context Protocol (MCP) を介してツールを公開する Kintone 書籍管理アプリケーションです。
プロジェクトをセットアップするには、以下の手順に従ってください。
リポジトリのクローン:
git clone <repository-url>
cd kintone-bookmanage-mcp依存関係のインストール:
npm install環境変数の設定:
プロジェクトのルートディレクトリに .env ファイルを作成し、以下の変数を設定します。
KINTONE_BASE_URL=YOUR_KINTONE_BASE_URL
KINTONE_API_TOKEN=YOUR_KINTONE_API_TOKEN
KINTONE_APP_ID=YOUR_KINTONE_APP_ID
KINTONE_REQUEST_FIELDS=YOUR_KINTONE_REQUEST_FIELDSプレースホルダーの値を実際の Kintone 環境の詳細に置き換えてください。
Related MCP server: microCMS MCP Server
アプリケーションを実行するには、まずビルドしてからサーバーを起動する必要があります。
プロジェクトのビルド:
npm run buildサーバーの起動:
node build/index.jsサーバーが起動し、MCP ツールが公開されます。
このアプリケーションは get-book-information という名前のツールを公開しており、mcp-cli (グローバルにインストールされている場合) を使用するか、build/index.js と直接やり取りすることで呼び出すことができます。
get-book-information ツールを呼び出すには (mcp-cli が利用可能で設定されていると仮定します):
mcp-cli call get-book-informationこれにより、Kintone アプリケーションから書籍レコードがフェッチされ、フォーマットされた情報が返されます。
{
"mcpServers": {
"books": {
"command": "node",
"args": ["/Users/tairiku/dev/kintone-bookmanage-mcp-stdin/build/index.js"]
}
}
}Get book information in the Information Systems Department
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are empty, so the description carries the full burden. It implies a read operation ('Get'), suggesting it's likely non-destructive, but doesn't disclose behavioral traits like authentication needs, rate limits, or what happens if no data is found. It adds basic context (department scope) but lacks critical details for a tool with no annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, straightforward sentence that efficiently states the tool's purpose and scope. It's appropriately sized and front-loaded, with no wasted words. However, it could be slightly more structured (e.g., separating purpose from context), but it's concise and clear.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It lacks details on what 'book information' includes, how results are returned, or any behavioral context. For a tool with no structured data, the description should compensate more to be fully helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0 parameters with 100% coverage, so no parameters need documentation. The description doesn't add param info, which is acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states the tool's purpose ('Get book information') and specifies the domain ('Information Systems Department'), which provides some context. However, it's vague about what 'book information' entails (e.g., metadata, availability, content) and doesn't differentiate from siblings (though none exist). It's not tautological but lacks specificity in verb+resource details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool, such as scenarios, prerequisites, or alternatives. It mentions the department scope ('Information Systems Department'), but this is part of the purpose, not usage instructions. Without explicit when/when-not or context, it offers minimal guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.0.0get-book-informationScored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose of retrieving book information.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get-book-information), which is appropriate and consistent within this minimal set.
A single tool for a book management system is too few for the apparent scope, as it only supports retrieval without create, update, delete, or other management operations. This severely limits functionality and indicates an incomplete tool surface.
The tool set is severely incomplete for a book management domain. It only provides a get operation, lacking essential CRUD operations like create, update, and delete, as well as other expected features such as searching or listing books, which will cause agent failures in typical management workflows.
MCP server for Russian books search, details, and recommendation candidates.
A Model Context Protocol (MCP) server for Selise Blocks Cloud integration
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
