MCP server for kintone サンプル

Created By
r3-yamauchia year ago
MCP server for kintone
Overview

what is kintone MCP Server?

The kintone MCP Server is a sample server designed for integration with kintone using the Model Context Protocol (MCP). It allows users to access and update kintone data through the Claude Desktop application.

how to use kintone MCP Server?

To use the kintone MCP Server, download the source code, install Node.js, run npm install, configure the Claude Desktop app, and restart the app to start using the server.

key features of kintone MCP Server?

  • Access and update kintone data via Claude Desktop.
  • Supports various record operations like create, update, and delete.
  • File upload and download capabilities.
  • App management features including creation and deployment.

use cases of kintone MCP Server?

  1. Automating data entry and updates in kintone applications.
  2. Integrating kintone with other applications using Claude.
  3. Managing kintone applications and their settings programmatically.

FAQ from kintone MCP Server?

  • What is required to use the kintone MCP Server?

You need a subscription to the Claude Pro plan and Node.js installed on your machine.

  • Can I use this server with other applications?

Yes, it can be integrated with other applications that support MCP.

  • Is there any support available for this server?

No, the server is provided as-is for informational purposes, and individual support is not available.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
r3-yamauchi
Star
6
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago