kintone MCP Server (Python3)

Created By
r3-yamauchia year ago
Overview

What is kintone MCP Server (Python3)?

The kintone MCP Server is a server designed to interact with the kintone REST API using the Model Context Protocol (MCP). It allows users to manage and retrieve records from kintone applications seamlessly.

How to use kintone MCP Server?

To use the kintone MCP Server, you can install it via pip or uvx, set up your environment variables, and then run the server using the recommended command.

Key features of kintone MCP Server?

  • Retrieve records from kintone applications.
  • Search and obtain application information.
  • Supports both API token and password authentication.
  • Automatic pagination handling.
  • Filtering capabilities through queries.
  • Executes all API requests using POST + X-HTTP-Method-Override.

Use cases of kintone MCP Server?

  1. Automating data retrieval from kintone applications.
  2. Integrating kintone with other services using the REST API.
  3. Building custom applications that require kintone data.

FAQ from kintone MCP Server?

  • What authentication methods are supported?

The server supports both API token and password authentication methods.

  • How do I install the server?

You can install it using pip install kintone-mcp-server-python3 or uvx kintone-mcp-server-python3.

  • Can I filter records when retrieving them?

Yes, you can use query strings to filter records based on specific criteria.

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

Recommend Servers

View All
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.

12 hours ago
Voyei

an hour ago