pomera-ai-commander 1.2.10 β†’ 1.2.11

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +90 -112
  2. package/mcp.json +1 -1
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,153 +1,131 @@
1
- # MCP Registry
1
+ # Pomera AI Commander (PAC)
2
2
 
3
- The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
3
+ <p align="center">
4
+ <img src="resources/icon.png" alt="Pomera - the fluffy Pomeranian mascot" width="128" height="128">
5
+ </p>
4
6
 
5
- [**πŸ“€ Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚑️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**πŸ‘€ Ecosystem vision**](docs/design/ecosystem-vision.md) | πŸ“– **[Full documentation](./docs)**
7
+ [![Download Latest Release](https://img.shields.io/badge/Download-Latest%20Release-blue?style=for-the-badge&logo=github)](https://github.com/matbanik/Pomera-AI-Commander/releases)
6
8
 
7
- ## Development Status
9
+ A desktop text "workbench" + MCP server: clean, transform, extract, and analyze text fastβ€”manually in a GUI or programmatically from AI assistants (Cursor / Claude Desktop / MCP clients).
8
10
 
9
- **2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** πŸŽ‰. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patienceβ€”your involvement has been key to getting us here!
11
+ > Hook: Stop pasting text into 10 random websites. Pomera gives you one place (GUI + MCP) to do the 90% text ops you repeat every week.
10
12
 
11
- **2025-09-08 update**: The registry has launched in preview πŸŽ‰ ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
13
+ [Download latest release](https://github.com/matbanik/Pomera-AI-Commander/releases) Β· Docs: [Tools](docs/TOOLS_DOCUMENTATION.md) Β· [MCP Guide](docs/MCP_SERVER_GUIDE.md) Β· [Troubleshooting](docs/TROUBLESHOOTING.md)
12
14
 
13
- Current key maintainers:
14
- - **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)
15
- - **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
16
- - **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
17
- - **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
15
+ ---
18
16
 
19
- ## Contributing
17
+ ## 60-second demo (what to expect)
18
+ ![Messy text β†’ clean output β†’ extracted URLs/emails β†’ ready to ship](PAC.gif)
20
19
 
21
- We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
20
+ **Best-for workflows**
21
+ - Cleaning pasted logs / PDFs (whitespace, wrapping, stats)
22
+ - Extracting emails/URLs/IDs via regex
23
+ - Normalizing case, sorting, columns
24
+ - Hashing/encoding utilities
25
+ - Letting Cursor/Claude call these as MCP tools in a repeatable pipeline
22
26
 
23
- Often (but not always) ideas flow through this pipeline:
27
+ ---
24
28
 
25
- - **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
26
- - **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
27
- - **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work
28
- - **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
29
+ ## Prerequisites
29
30
 
30
- ### Quick start:
31
-
32
- #### Pre-requisites
33
-
34
- - **Docker**
35
- - **Go 1.24.x**
36
- - **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
37
- - **golangci-lint v2.4.0**
38
-
39
- #### Running the server
31
+ **Python 3.8+** is required for all installation methods.
40
32
 
33
+ ### macOS (Homebrew)
41
34
  ```bash
42
- # Start full development environment
43
- make dev-compose
35
+ # Tkinter support (replace @3.14 with your Python version)
36
+ brew install python-tk@3.14
37
+ pip3 install requests reportlab python-docx
44
38
  ```
45
39
 
46
- This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
47
-
48
- **Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
49
-
50
- By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
51
-
52
- The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
53
-
54
- <details>
55
- <summary>Alternative: Running a pre-built Docker image</summary>
56
-
57
- Pre-built Docker images are automatically published to GitHub Container Registry:
58
-
40
+ ### Ubuntu/Debian
59
41
  ```bash
60
- # Run latest stable release
61
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
62
-
63
- # Run latest from main branch (continuous deployment)
64
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
65
-
66
- # Run specific release version
67
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
68
-
69
- # Run development build from main branch
70
- docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
42
+ sudo apt-get install python3-tk
43
+ pip3 install requests reportlab python-docx
71
44
  ```
72
45
 
73
- **Available tags:**
74
- - **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
75
- - **Continuous**: `main` (latest main branch build)
76
- - **Development**: `main-<date>-<sha>` (specific commit builds)
46
+ ### Windows
47
+ Tkinter is included with Python from [python.org](https://python.org).
48
+ ```cmd
49
+ pip install requests reportlab python-docx
50
+ ```
77
51
 
78
- </details>
52
+ > **Note:** For PEP 668 protected environments, use `pip3 install --user` or a virtual environment.
79
53
 
80
- #### Publishing a server
54
+ ---
81
55
 
82
- To publish a server, we've built a simple CLI. You can use it with:
56
+ ## Install / Run
57
+ ### Option A β€” Prebuilt executable (recommended)
58
+ [Download from Releases](https://github.com/matbanik/Pomera-AI-Commander/releases) and run.
83
59
 
60
+ ### Option B β€” Python (PyPI)
84
61
  ```bash
85
- # Build the latest CLI
86
- make publisher
87
-
88
- # Use it!
89
- ./bin/mcp-publisher --help
62
+ pip install pomera-ai-commander
63
+ # then run:
64
+ pomera-ai-commander --help
90
65
  ```
91
66
 
92
- See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
67
+ ### Option C β€” Node.js (npm)
68
+ ```bash
69
+ npm install -g pomera-ai-commander
70
+ # then run:
71
+ pomera-mcp --help
72
+ ```
93
73
 
94
- #### Other commands
74
+ ### Create Desktop Shortcut
75
+ After installing via pip or npm, create a desktop shortcut for quick access:
95
76
 
96
77
  ```bash
97
- # Run lint, unit tests and integration tests
98
- make check
99
- ```
78
+ # For pip install:
79
+ pomera-create-shortcut
100
80
 
101
- There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
81
+ # For npm install (from package directory):
82
+ python create_shortcut.py
83
+ ```
102
84
 
103
- <!--
104
- For Claude and other AI tools: Always prefer make targets over custom commands where possible.
105
- -->
85
+ ---
106
86
 
107
- ## Architecture
87
+ ## MCP Server for AI Assistants
108
88
 
109
- ### Project Structure
89
+ Pomera exposes 22 text processing tools via MCP. Configure your AI assistant:
110
90
 
111
- ```
112
- β”œβ”€β”€ cmd/ # Application entry points
113
- β”‚ └── publisher/ # Server publishing tool
114
- β”œβ”€β”€ data/ # Seed data
115
- β”œβ”€β”€ deploy/ # Deployment configuration (Pulumi)
116
- β”œβ”€β”€ docs/ # Documentation
117
- β”œβ”€β”€ internal/ # Private application code
118
- β”‚ β”œβ”€β”€ api/ # HTTP handlers and routing
119
- β”‚ β”œβ”€β”€ auth/ # Authentication (GitHub OAuth, JWT, namespace blocking)
120
- β”‚ β”œβ”€β”€ config/ # Configuration management
121
- β”‚ β”œβ”€β”€ database/ # Data persistence (PostgreSQL)
122
- β”‚ β”œβ”€β”€ service/ # Business logic
123
- β”‚ β”œβ”€β”€ telemetry/ # Metrics and monitoring
124
- β”‚ └── validators/ # Input validation
125
- β”œβ”€β”€ pkg/ # Public packages
126
- β”‚ β”œβ”€β”€ api/ # API types and structures
127
- β”‚ β”‚ └── v0/ # Version 0 API types
128
- β”‚ └── model/ # Data models for server.json
129
- β”œβ”€β”€ scripts/ # Development and testing scripts
130
- β”œβ”€β”€ tests/ # Integration tests
131
- └── tools/ # CLI tools and utilities
132
- └── validate-*.sh # Schema validation tools
91
+ **Cursor** (`.cursor/mcp.json`):
92
+ ```json
93
+ {
94
+ "mcpServers": {
95
+ "pomera": {
96
+ "command": "pomera-ai-commander"
97
+ }
98
+ }
99
+ }
133
100
  ```
134
101
 
135
- ### Authentication
102
+ **Claude Desktop** (`claude_desktop_config.json`):
103
+ ```json
104
+ {
105
+ "mcpServers": {
106
+ "pomera": {
107
+ "command": "pomera-ai-commander"
108
+ }
109
+ }
110
+ }
111
+ ```
136
112
 
137
- Publishing supports multiple authentication methods:
138
- - **GitHub OAuth** - For publishing by logging into GitHub
139
- - **GitHub OIDC** - For publishing from GitHub Actions
140
- - **DNS verification** - For proving ownership of a domain and its subdomains
141
- - **HTTP verification** - For proving ownership of a domain
113
+ > **πŸ’‘ Tip:** If the simple command doesn't work, use the full path. Find it with:
114
+ > ```bash
115
+ > # For npm install:
116
+ > npm root -g
117
+ > # Then use: <result>/pomera-ai-commander/pomera_mcp_server.py
118
+ >
119
+ > # For pip install:
120
+ > pip show pomera-ai-commander | grep Location
121
+ > ```
142
122
 
143
- The registry validates namespace ownership when publishing. E.g. to publish...:
144
- - `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
145
- - `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
123
+ See the full [MCP Server Guide](docs/MCP_SERVER_GUIDE.md) for Antigravity, executable configs, and troubleshooting.
146
124
 
147
- ## Community Projects
125
+ <!-- mcp-name: io.github.matbanik/pomera -->
148
126
 
149
- Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
127
+ ---
150
128
 
151
- ## More documentation
129
+ ## License
152
130
 
153
- See the [documentation](./docs) for more details if your question has not been answered here!
131
+ MIT License - see [LICENSE](LICENSE) for details.
package/mcp.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pomera-ai-commander",
3
- "version": "1.2.10",
3
+ "version": "1.2.11",
4
4
  "description": "Text processing toolkit with 22 MCP tools including case transformation, encoding, hashing, text analysis, and notes management for AI assistants.",
5
5
  "homepage": "https://github.com/matbanik/Pomera-AI-Commander",
6
6
  "repository": "https://github.com/matbanik/Pomera-AI-Commander",
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "pomera-ai-commander",
3
3
  "mcpName": "io.github.matbanik/pomera",
4
- "version": "1.2.10",
4
+ "version": "1.2.11",
5
5
  "description": "Text processing toolkit with 22 MCP tools for AI assistants - case transformation, encoding, hashing, text analysis, and notes management",
6
6
  "main": "pomera_mcp_server.py",
7
7
  "bin": {