This MCP server, Connpass User MCP Server, provides Tools to fetch and aggregate information from Connpass user profiles. The server exposes tools such as get_connpass_user_list, get_connpass_user_group_list, get_connpass_user_events, and get_connpass_user_presenter_events. Each tool queries Connpass for a given nickname and returns structured data about user basics, groups, participated events, and presenter events, respectively. To use these tools, supply the target nickname(s) and read the returned data which includes counts (events participated/managed/presented, group membership) and detailed event or group metadata. For example, you can ask the MCP server for a user’s basic profile and their recent events, or request the list of groups a user belongs to. The server is designed to work with both individual nicknames and lists, enabling batch queries if supported by the client configuration.

Prerequisites:

• A host environment with Node, Deno, and/or Docker as needed by your setup (the recommended path uses Deno).
• Access to Connpass API key (CONNPASS_API_KEY).
• Git to clone the repository.

Installation steps:

1. Clone the repository: git clone https://github.com/yamanoku/connpass-user-mcp-server.git
2. Copy the environment example and set your API key: cp .env.example .env

   edit .env to set CONNPASS_API_KEY

3. Install dependencies and prepare the server (depending on the chosen runtime):
   • Deno (recommended):
     • Ensure Deno is installed at the path shown in the README (e.g., /home/user/.deno/bin/deno).
   • Node.js (alternative):
     • npm ci
     • npm run build
4. Start the MCP server using the preferred method (examples from README):
   • Deno (recommended): Run the MCP server via the Deno entrypoint with appropriate permissions and env file.
   • Docker (optional): Build and run the Docker image, providing CONNPASS_API_KEY as an environment variable.

Note: If you plan to use npx, be aware of security warnings noted in the README; prefer a local install or Docker for production use.

Tips and considerations:

• Ensure CONNPASS_API_KEY is kept secure and not committed to version control.
• The Deno setup requires --allow-net for connpass.com access and --env-file to load API keys; adjust paths as needed for your environment.
• When using Docker, pass the API key via -e CONNPASS_API_KEY=... to ensure the server can authenticate with Connpass.
• The npx option is deprecated in the README due to supply chain concerns; prefer local or Docker deployments.
• If you run into CORS or network restrictions, verify that your environment permits outbound HTTP requests to connpass.com.