Skip to main content
Glama
Azhar-obenan

Obenan MCP Server

by Azhar-obenan
README.md
# obenan-mcp-server MCP server

obenan mcp server

## Components

### Resources

The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype

### Prompts

The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
  - Optional "style" argument to control detail level (brief/detailed)
  - Generates prompt combining all current notes with style preference

### Tools

The server implements one tool:
- add-note: Adds a new note to the server
  - Takes "name" and "content" as required string arguments
  - Updates server state and notifies clients of resource changes

## Configuration

[TODO: Add configuration details specific to your implementation]

## Quickstart

### Install

#### Claude Desktop

On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

<details>
  <summary>Development/Unpublished Servers Configuration</summary>
  ```
  "mcpServers": {
    "obenan-mcp-server": {
      "command": "uv",
      "args": [
        "--directory",
        "/Users/AhmedUmerAnees/code/obenan-mcp-server",
        "run",
        "obenan-mcp-server"
      ]
    }
  }
  ```
</details>

<details>
  <summary>Published Servers Configuration</summary>
  ```
  "mcpServers": {
    "obenan-mcp-server": {
      "command": "uvx",
      "args": [
        "obenan-mcp-server"
      ]
    }
  }
  ```
</details>

## Development

### Building and Publishing

To prepare the package for distribution:

1. Sync dependencies and update lockfile:
```bash
uv sync
```

2. Build package distributions:
```bash
uv build
```

This will create source and wheel distributions in the `dist/` directory.

3. Publish to PyPI:
```bash
uv publish
```

Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`

### Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).


You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:

```bash
npx @modelcontextprotocol/inspector uv --directory /Users/AhmedUmerAnees/code/obenan-mcp-server run obenan-mcp-server
```


Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues