MCP Server for cli-kintone

Created By
r3-yamauchia year ago
これは cli-kintone を MCP (Model Context Protocol) Server化できないかという発想をもとに検証している実験的なリポジトリです。
Overview

What is MCP Server for cli-kintone?

MCP Server for cli-kintone is an experimental repository aimed at transforming cli-kintone into a Model Context Protocol (MCP) server.

How to use MCP Server for cli-kintone?

To use the MCP Server, clone the repository, install dependencies, and create an MCP configuration file with your Kintone credentials. You can then call the server using an AI assistant or directly through the command line.

Key features of MCP Server for cli-kintone?

  • Supports fetching records from Kintone applications using the get_records function.
  • Allows authentication via username/password or API tokens.
  • Configurable MCP settings for different environments.

Use cases of MCP Server for cli-kintone?

  1. Retrieving records from Kintone applications for data analysis.
  2. Integrating Kintone with AI tools for automated data processing.
  3. Facilitating the creation and management of Kintone records through a command-line interface.

FAQ from MCP Server for cli-kintone?

  • What is the maximum number of API tokens I can use?

You can specify up to 9 API tokens in a single request. Exceeding this limit will result in an error.

  • Is there a license for this project?

Yes, the project is licensed under the MIT license.

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

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago