pomera-ai-commander 1.2.9 β 1.2.10
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.
- package/README.md +113 -89
- package/mcp.json +1 -1
- package/package.json +2 -1
package/README.md
CHANGED
|
@@ -1,129 +1,153 @@
|
|
|
1
|
-
#
|
|
1
|
+
# MCP Registry
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
<img src="resources/icon.png" alt="Pomera - the fluffy Pomeranian mascot" width="128" height="128">
|
|
5
|
-
</p>
|
|
3
|
+
The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
|
|
6
4
|
|
|
7
|
-
[
|
|
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)**
|
|
8
6
|
|
|
9
|
-
|
|
7
|
+
## Development Status
|
|
10
8
|
|
|
11
|
-
|
|
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!
|
|
12
10
|
|
|
13
|
-
[
|
|
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)).
|
|
14
12
|
|
|
15
|
-
|
|
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)
|
|
16
18
|
|
|
17
|
-
##
|
|
18
|
-
|
|
19
|
+
## Contributing
|
|
19
20
|
|
|
20
|
-
|
|
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
|
|
21
|
+
We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
|
|
26
22
|
|
|
27
|
-
|
|
23
|
+
Often (but not always) ideas flow through this pipeline:
|
|
28
24
|
|
|
29
|
-
|
|
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
|
|
30
29
|
|
|
31
|
-
|
|
30
|
+
### Quick start:
|
|
32
31
|
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
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
|
|
39
40
|
|
|
40
|
-
### Ubuntu/Debian
|
|
41
41
|
```bash
|
|
42
|
-
|
|
43
|
-
|
|
42
|
+
# Start full development environment
|
|
43
|
+
make dev-compose
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
pip install requests reportlab python-docx
|
|
50
|
-
```
|
|
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.
|
|
51
49
|
|
|
52
|
-
|
|
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`.
|
|
53
51
|
|
|
54
|
-
|
|
52
|
+
The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
|
|
55
53
|
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
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:
|
|
59
58
|
|
|
60
|
-
### Option B β Python (PyPI)
|
|
61
59
|
```bash
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
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
|
|
65
71
|
```
|
|
66
72
|
|
|
67
|
-
|
|
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)
|
|
77
|
+
|
|
78
|
+
</details>
|
|
79
|
+
|
|
80
|
+
#### Publishing a server
|
|
81
|
+
|
|
82
|
+
To publish a server, we've built a simple CLI. You can use it with:
|
|
83
|
+
|
|
68
84
|
```bash
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
85
|
+
# Build the latest CLI
|
|
86
|
+
make publisher
|
|
87
|
+
|
|
88
|
+
# Use it!
|
|
89
|
+
./bin/mcp-publisher --help
|
|
72
90
|
```
|
|
73
91
|
|
|
74
|
-
|
|
75
|
-
After installing via pip or npm, create a desktop shortcut for quick access:
|
|
92
|
+
See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
|
|
76
93
|
|
|
77
|
-
|
|
78
|
-
# For pip install:
|
|
79
|
-
pomera-create-shortcut
|
|
94
|
+
#### Other commands
|
|
80
95
|
|
|
81
|
-
|
|
82
|
-
|
|
96
|
+
```bash
|
|
97
|
+
# Run lint, unit tests and integration tests
|
|
98
|
+
make check
|
|
83
99
|
```
|
|
84
100
|
|
|
85
|
-
|
|
101
|
+
There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
|
|
86
102
|
|
|
87
|
-
|
|
103
|
+
<!--
|
|
104
|
+
For Claude and other AI tools: Always prefer make targets over custom commands where possible.
|
|
105
|
+
-->
|
|
88
106
|
|
|
89
|
-
|
|
107
|
+
## Architecture
|
|
90
108
|
|
|
91
|
-
|
|
92
|
-
```json
|
|
93
|
-
{
|
|
94
|
-
"mcpServers": {
|
|
95
|
-
"pomera": {
|
|
96
|
-
"command": "pomera-ai-commander"
|
|
97
|
-
}
|
|
98
|
-
}
|
|
99
|
-
}
|
|
100
|
-
```
|
|
109
|
+
### Project Structure
|
|
101
110
|
|
|
102
|
-
**Claude Desktop** (`claude_desktop_config.json`):
|
|
103
|
-
```json
|
|
104
|
-
{
|
|
105
|
-
"mcpServers": {
|
|
106
|
-
"pomera": {
|
|
107
|
-
"command": "pomera-ai-commander"
|
|
108
|
-
}
|
|
109
|
-
}
|
|
110
|
-
}
|
|
111
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
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
### Authentication
|
|
136
|
+
|
|
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
|
|
112
142
|
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
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
|
-
> ```
|
|
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
|
|
122
146
|
|
|
123
|
-
|
|
147
|
+
## Community Projects
|
|
124
148
|
|
|
125
|
-
|
|
149
|
+
Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
|
|
126
150
|
|
|
127
|
-
##
|
|
151
|
+
## More documentation
|
|
128
152
|
|
|
129
|
-
|
|
153
|
+
See the [documentation](./docs) for more details if your question has not been answered here!
|
package/mcp.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pomera-ai-commander",
|
|
3
|
-
"version": "1.2.
|
|
3
|
+
"version": "1.2.10",
|
|
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,6 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pomera-ai-commander",
|
|
3
|
-
"
|
|
3
|
+
"mcpName": "io.github.matbanik/pomera",
|
|
4
|
+
"version": "1.2.10",
|
|
4
5
|
"description": "Text processing toolkit with 22 MCP tools for AI assistants - case transformation, encoding, hashing, text analysis, and notes management",
|
|
5
6
|
"main": "pomera_mcp_server.py",
|
|
6
7
|
"bin": {
|