Obenan MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | Your token used for publishing to PyPI | |
| UV_PUBLISH_PASSWORD | No | Your password for publishing to PyPI | |
| UV_PUBLISH_USERNAME | No | Your username for publishing to PyPI |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_my_locationsC | Fetch locations from Obenan API using the access token |
| get_location_detailsC | Get detailed information about a specific location by ID |
| search_locations_by_nameB | Search for locations containing a specific name and allow selection to get details |
| review_analyzerC | Analyze reviews using the Obenan Review Analyzer API |
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 has a clearly distinct purpose with no overlap: fetch_my_locations retrieves all locations, get_location_details provides details for a specific location, review_analyzer analyzes reviews, and search_locations_by_name searches by name. The descriptions clearly differentiate these functions, making tool selection unambiguous.
The naming is mostly consistent with a verb_noun pattern (fetch_my_locations, get_location_details, search_locations_by_name), but review_analyzer deviates slightly by using a noun_verb structure. This minor inconsistency does not significantly impact readability or predictability.
With 4 tools, this server is well-scoped for managing locations and reviews. Each tool serves a distinct and necessary function, and the count is appropriate for the domain without being too sparse or bloated.
The toolset covers core operations for location management (fetch, get details, search) and review analysis, but there are minor gaps such as missing CRUD operations for locations (e.g., create, update, delete) and reviews. However, agents can work effectively with the provided tools for basic workflows.