MCP.so
登录

mcp-jp — Japanese SMB SaaS connectors

@mediiiiium

关于 mcp-jp — Japanese SMB SaaS connectors

MCP servers for Japanese SMB SaaS that have no official MCP. 30+ connectors (KING OF TIME, SmartHR, kaonavi, Smaregi, CloudSign, L Step, etc.) for attendance, HR, invoicing, POS, e-contracts and more. Each is an independent pip package; connectors are archived once an official MC

基本信息

分类

其他

传输方式

stdio

发布者

mediiiiium

提交者

mediiiiium

配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "smarthr": {
      "command": "smarthr-mcp",
      "env": {
        "SMARTHR_CLIENT_ID": "your_client_id",
        "SMARTHR_CLIENT_SECRET": "your_client_secret",
        "SMARTHR_SUBDOMAIN": "your_subdomain"
      }
    }
  }
}

工具

未检测到工具

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is mcp-jp?

mcp-jp is a monorepo of over 30 independent MCP server connectors for Japanese SMB SaaS that have no official MCP. It covers attendance, HR, invoicing, POS, e-contracts, CRM, and more.

How to use mcp-jp?

Each connector is an independent pip package. To use one, navigate to its directory (e.g., cd smarthr) and run pip install -e .. Then configure that connector in your MCP client using its command and environment variables as described in each connector’s README.

Key features of mcp-jp

  • 30+ independent connectors for Japanese SMB SaaS.
  • Covers KING OF TIME, AKASHI, HRMOS, SmartHR, kaonavi, Smaregi, CloudSign, Misoca, MakeLeaps, board, invox, L Step, LINE WORKS, and more.
  • Each connector is a separate pip package with approximately 5 tools.
  • Connectors built only for services lacking an official MCP.
  • Connectors are moved to archive/ once an official MCP ships.

Use cases of mcp-jp

  • Retrieve attendance records from KING OF TIME or AKASHI.
  • Access employee HR data via SmartHR or kaonavi.
  • Pull sales or invoicing data from Misoca, MakeLeaps, board, or invox.
  • Integrate with POS systems like Smaregi.
  • Manage e-contracts through CloudSign.
  • Interact with LINE WORKS or L Step for business communications.

FAQ from mcp-jp

How does mcp-jp differ from official MCP servers?

mcp-jp provides connectors specifically for Japanese SMB SaaS that do not yet have an official MCP. Once a service releases an official MCP, its connector is archived.

What runtime or dependencies are required?

Each connector is a Python pip package. You need Python and pip installed, then run pip install -e . inside the connector’s directory.

Where do user credentials or data reside?

Credentials are handled per connector via environment variables (configured in your MCP client). Data is retrieved from the respective SaaS APIs; no local storage is described.

Are there any known limits?

The README does not list specific limits beyond noting that each connector is independent and must be configured one at a time.

What transports or authentication methods are supported?

Authentication details vary by connector. Refer to each connector’s own README for its required environment variables and command configuration.

评论

其他 分类下的更多 MCP 服务器