connpass-user-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONNPASS_API_KEY | Yes | Your Connpass API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connpass_user_listC | Fetch Connpass user information |
| get_connpass_user_group_listC | Fetch Connpass user group information |
| get_connpass_user_eventsC | Fetch events for a specific Connpass user |
| get_connpass_user_presenter_eventsA | Fetch presenter events for a specific Connpass user |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of Connpass user data: user info, user groups, user's events, and user's presenter events. The descriptions clearly differentiate the resource types, so an agent is unlikely to select the wrong tool.
All tools follow the 'get_connpass_user_' prefix, but the resource nouns vary slightly in style ('list' vs 'group_list' vs 'events'). The pattern is consistent enough, though 'user_list' is a bit ambiguous compared to the other clearly resource-specific names.
With only 4 tools, the server is well-scoped and focused on read-only Connpass user information. Each tool covers a distinct data need without unnecessary bloat, fitting comfortably within the ideal 3-15 range.
The server covers the core user-oriented resources: profile, groups, events, and presenter events. Minor gaps like attendee history or bookmarks could exist, but for a typical read-only user information server, this is a reasonable and functional surface.