Connpass User MCP Server

Created By
yamanokua year ago
Model Context Protocol server that provides connpass users API v2
Overview

What is Connpass User MCP Server?

Connpass User MCP Server is a Model Context Protocol server that provides an API for accessing Connpass user information and event participation details.

How to use Connpass User MCP Server?

To use the server, you need to set up your environment by obtaining a Connpass API key, configuring the necessary environment variables, and starting the server using the provided command.

Key features of Connpass User MCP Server?

  • get_connpass_user_list: Retrieve basic information about Connpass users.
  • get_connpass_user_group_list: Get a list of groups that a Connpass user belongs to.
  • get_connpass_user_events: Fetch event information for events a Connpass user has participated in.
  • get_connpass_user_presenter_events: Access information about events where a Connpass user was a presenter.

Use cases of Connpass User MCP Server?

  1. Fetching user details for event organizers.
  2. Analyzing user participation in events.
  3. Managing user groups and their activities.

FAQ from Connpass User MCP Server?

  • How do I obtain a Connpass API key?

You can obtain a Connpass API key by following the instructions on the Connpass API usage page.

  • What programming language is used for this server?

The server is implemented in TypeScript.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yamanoku
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago