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

8 hours ago