MCP server for kintone

Created By
macrata year ago
MCP server for kintone
Overview

what is MCP server for kintone?

The MCP server for kintone is a server implementation that allows you to interface with kintone data using AI tools, specifically designed for leveraging the Model Context Protocol (MCP).

how to use MCP server for kintone?

To use the MCP server, you need to build it from the source and configure it with your kintone credentials and app details. Then connect it to an AI client like Claude Desktop to interact with your kintone data.

key features of MCP server for kintone?

  • Allows interaction with kintone apps through AI tools.
  • Configurable with various permissions and app data access.
  • Requires minimal setup with a clear JSON configuration file.

use cases of MCP server for kintone?

  1. Integrating kintone data with AI-powered applications and automation tasks.
  2. Enhancing productivity by using AI tools to manipulate and analyze data from kintone.
  3. Allowing for customized AI interactions based on kintone app configurations.

FAQ from MCP server for kintone?

  • Is MCP server for kintone easy to set up?

Yes! It requires building from source and a JSON configuration but is straightforward to configure.

  • Does it support all types of kintone apps?

The server can be configured to connect to specific apps as defined in the JSON configuration file.

  • Can I use any AI tool with this server?

Yes, as long as the AI tool supports the Model Context Protocol, it should work seamlessly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
macrat
Star
9
Language
Go
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)

2 days ago