Connpass User MCP Server

Model Context Protocol server that provides connpass users API v2

Local serverstdioTypeScript

What is the Connpass User MCP server?

Model Context Protocol server that provides connpass users API v2. The connpass user mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

Its toolset

Everything the assistant can do here goes through one of these:

  • get_connpass_user_list — Connpassユーザーの基本情報を取得します
  • get_connpass_user_group_list — Connpassユーザーが所属するグループ一覧を取得します
  • get_connpass_user_events — Connpassユーザーが参加したイベント情報を取得します
  • get_connpass_user_presenter_events — Connpassユーザーが発表者として参加したイベント情報を取得します
  • Tools — The Tools tool exposed by this server

Configuration

You will need one environment variable: CONNPASS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at @yamanoku/connpass-user-mcp-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Connpass User's toolset — get_connpass_user_list, get_connpass_user_group_list, get_connpass_user_events and 2 more — is a fair guide to whether it matches your workflow. It is maintained by yamanoku; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the connpass user mcp server does with a few real requests.

Available tools

ToolWhat it does
get_connpass_user_listConnpassユーザーの基本情報を取得します
get_connpass_user_group_listConnpassユーザーが所属するグループ一覧を取得します
get_connpass_user_eventsConnpassユーザーが参加したイベント情報を取得します
get_connpass_user_presenter_eventsConnpassユーザーが発表者として参加したイベント情報を取得します
ToolsThe Tools tool exposed by this server.

How to install the Connpass User MCP server

{
  "mcpServers": {
    "connpass-user": {
      "command": "npx",
      "args": ["-y", "@yamanoku/connpass-user-mcp-server"],
      "env": {
        "CONNPASS_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
CONNPASS_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Connpass User to get connpass user list.
  • Use Connpass User to get connpass user group list.
  • Use Connpass User to get connpass user events.

Frequently asked questions

It can run on Deno (recommended) or Node.js, and also supports Docker and npx-based execution.