Add 0nMCP — Universal AI API Orchestrator (564 tools, 26 services) - #312
Add 0nMCP — Universal AI API Orchestrator (564 tools, 26 services)#312Crypto-Goatz wants to merge 1 commit into
Conversation
Review Summary by QodoAdd 0nMCP Universal AI API Orchestrator server
WalkthroughsDescription• Add 0nMCP server with 564 tools across 26 services • Supports Stripe, Slack, Discord, SendGrid, GitHub, Shopify integration • Includes natural language AI orchestration capabilities • Provides npm installation with optional Anthropic API key Diagramflowchart LR
A["0nMCP Server"] -- "564 tools" --> B["26 Services"]
B -- "includes" --> C["Stripe, Slack, Discord"]
B -- "includes" --> D["GitHub, Shopify, Gmail"]
A -- "installation" --> E["npm npx command"]
A -- "features" --> F["AI Orchestration & Encryption"]
File Changes1. mcp-registry/servers/0nmcp.json
|
Code Review by Qodo
1. Invalid category value
|
📝 WalkthroughWalkthroughA new server manifest JSON file is added at Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2e430f8e27
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "license": "MIT", | ||
| "categories": [ | ||
| "Dev Tools", | ||
| "Automation" |
There was a problem hiding this comment.
The category "Automation" is not one of the allowed values in mcp-registry/schema/server-schema.json (the enum lists values like "Dev Tools", "AI Systems", etc.), so this manifest will fail the schema validation job configured in .github/workflows/test.yml for pull requests. As written, this blocks the registry entry from passing CI until the category is changed to a schema-supported value.
Useful? React with 👍 / 👎.
| "ANTHROPIC_API_KEY": { | ||
| "description": "Optional — enables AI-powered multi-step planning", | ||
| "required": false | ||
| } |
There was a problem hiding this comment.
Under installations.*.env, the schema requires each environment variable value to be a string, but ANTHROPIC_API_KEY is defined as an object (description/required). This violates mcp-registry/schema/server-schema.json and will cause the pull-request schema validation workflow (.github/workflows/test.yml) to fail for this manifest.
Useful? React with 👍 / 👎.
![qodo-code-review[bot]](https://avatars.githubusercontent.com/in/484649?s=60&v=4){kind=small}
| "categories": [ | ||
| "Dev Tools", | ||
| "Automation" | ||
| ], |
There was a problem hiding this comment.
1. Invalid category value 🐞 Bug ✓ Correctness
The manifest includes category "Automation", which is not in the schema’s allowed categories enum. This will fail the CI schema validation job that checks all mcp-registry/servers/*.json files.
Agent Prompt
### Issue description
`mcp-registry/servers/0nmcp.json` uses a category value ("Automation") that is not allowed by the registry schema enum, causing CI schema validation to fail.
### Issue Context
The CI workflow validates all manifests against `mcp-registry/schema/server-schema.json`, which defines an enum list for `categories`.
### Fix Focus Areas
- mcp-registry/servers/0nmcp.json[14-17]
- mcp-registry/schema/server-schema.json[70-90]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
| "env": { | ||
| "ANTHROPIC_API_KEY": { | ||
| "description": "Optional — enables AI-powered multi-step planning", | ||
| "required": false | ||
| } | ||
| }, |
There was a problem hiding this comment.
2. Installations.env type mismatch 🐞 Bug ⛯ Reliability
installations.npm.env is defined as an object-of-objects with description/required, but the schema and runtime code expect env to be a simple map of string-to-string. This will fail CI schema validation and can crash mcpm when constructing FullServerConfig.
Agent Prompt
### Issue description
The manifest encodes env var metadata inside `installations.npm.env`, but the registry schema requires `env` values to be strings and `mcpm` runtime expects `env: Dict[str,str]`. This breaks CI validation and may crash installs.
### Issue Context
Other manifests store env var metadata under top-level `arguments` and keep `installations.*.env` as a string-to-string mapping (typically using `${VAR}` templates).
### Fix Focus Areas
- mcp-registry/servers/0nmcp.json[30-47]
- mcp-registry/schema/server-schema.json[214-295]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
mcp-registry/servers/0nmcp.json (1)
34-37: Consider pinning the npm package version if stricter reproducibility is required.At Line 36,
0nmcpwithout a version pin allowsnpxto pull different versions over time. While version pinning improves reproducibility, it is not consistently enforced across the registry (many entries remain unpinned). If pinning is preferred, use0nmcp@1.0.0based on the current published version.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@mcp-registry/servers/0nmcp.json` around lines 34 - 37, The args entry currently passes the package name "0nmcp" to npx which allows floating installs; update the args array used by the registry entry (the "-y" and "0nmcp" elements) to pin the package to the desired release (e.g., change "0nmcp" to "0nmcp@1.0.0") so npx will install a fixed version for reproducible runs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@mcp-registry/servers/0nmcp.json`:
- Around line 55-58: Update the example prompt under the "Service Connection"
object: replace the production-style example key string "sk_live_xxx" with a
test-key example such as "sk_test_xxx" and append an explicit safety cue like
"—never share live/production keys" (or similar) in the "prompt" value to
discourage sharing real secrets; locate the "prompt" field within the object
titled "Service Connection" and modify its string accordingly.
---
Nitpick comments:
In `@mcp-registry/servers/0nmcp.json`:
- Around line 34-37: The args entry currently passes the package name "0nmcp" to
npx which allows floating installs; update the args array used by the registry
entry (the "-y" and "0nmcp" elements) to pin the package to the desired release
(e.g., change "0nmcp" to "0nmcp@1.0.0") so npx will install a fixed version for
reproducible runs.
| "title": "Service Connection", | ||
| "description": "Connect to a service with your API key", | ||
| "prompt": "Connect to Stripe with key sk_live_xxx" | ||
| }, |
There was a problem hiding this comment.
Do not model live secret sharing in example prompts.
Line 57 uses sk_live_xxx, which encourages entering production-style keys in chat contexts. Replace with test-key wording and an explicit “never share live keys” cue.
Proposed diff
{
"title": "Service Connection",
- "description": "Connect to a service with your API key",
- "prompt": "Connect to Stripe with key sk_live_xxx"
+ "description": "Connect to a service using a test API key (never share live keys)",
+ "prompt": "Connect to Stripe using test key sk_test_xxx"
},📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "title": "Service Connection", | |
| "description": "Connect to a service with your API key", | |
| "prompt": "Connect to Stripe with key sk_live_xxx" | |
| }, | |
| "title": "Service Connection", | |
| "description": "Connect to a service using a test API key (never share live keys)", | |
| "prompt": "Connect to Stripe using test key sk_test_xxx" | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@mcp-registry/servers/0nmcp.json` around lines 55 - 58, Update the example
prompt under the "Service Connection" object: replace the production-style
example key string "sk_live_xxx" with a test-key example such as "sk_test_xxx"
and append an explicit safety cue like "—never share live/production keys" (or
similar) in the "prompt" value to discourage sharing real secrets; locate the
"prompt" field within the object titled "Service Connection" and modify its
string accordingly.
1 participant
New Server: 0nMCP
564 tools. 26 services. 13 categories. Zero configuration.
npx 0nmcp(npmjs.com/package/0nmcp)io.github.0nork/0nMCPv2.1.0The most comprehensive MCP server available — 564 tools across 26 services including Stripe, Slack, Discord, SendGrid, GitHub, Shopify, Gmail, Google Sheets, Google Drive, Jira, Zendesk, Mailchimp, Zoom, Microsoft 365, MongoDB, and a 245-tool CRM integration.
Installation
Learn more at 0nmcp.com