Skip to content

Add OpenPost MCP server - #366

Open
rodrgds wants to merge 2 commits into
pathintegral-institute:mainfrom
rodrgds:add-openpost-mcp
Open

Add OpenPost MCP server#366
rodrgds wants to merge 2 commits into
pathintegral-institute:mainfrom
rodrgds:add-openpost-mcp

Conversation

@rodrgds

@rodrgds rodrgds commented Jul 26, 2026

Copy link
Copy Markdown

Adds OpenPost's official hosted MCP server to the registry. The manifest uses the repository's HTTP installation type for the OAuth-enabled Streamable HTTP endpoint and includes grounded usage examples.

Validation: uv run --with jsonschema python scripts/validate_manifest.py reports ✓ openpost: Valid across 382 manifests.

Disclosure: I maintain OpenPost.

Summary by CodeRabbit

  • New Features
    • Added the official OpenPost MCP server to the registry.
    • Published complete server details including metadata, categories, tags, licensing, repository, and homepage.
    • Added a recommended HTTP installation option with OAuth discovery support.
    • Included example prompts to help demonstrate typical OpenPost usage.

Copilot AI review requested due to automatic review settings July 26, 2026 17:44
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4b35dbe3-e4ed-4d3a-b4aa-85cf90eaa988

📥 Commits

Reviewing files that changed from the base of the PR and between 84ee032 and 02c2a04.

📒 Files selected for processing (1)
  • mcp-registry/servers/openpost.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • mcp-registry/servers/openpost.json

📝 Walkthrough

Walkthrough

Adds an official OpenPost MCP server registry entry with metadata, classifications, a recommended OAuth-discovery HTTP installation endpoint, example prompts, and repository information.

Changes

OpenPost MCP registry

Layer / File(s) Summary
OpenPost server definition
mcp-registry/servers/openpost.json
Adds server metadata, repository and licensing details, category and tag classifications, a recommended hosted HTTP installation with OAuth discovery, example prompts, and is_official: true.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested labels: Review effort 2/5, released

Suggested reviewers: copilot

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: adding the OpenPost MCP server entry to the registry.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@qodo-code-review

Copy link
Copy Markdown
Contributor

PR Summary by Qodo

Add OpenPost hosted MCP server manifest to registry

✨ Enhancement ⚙️ Configuration changes 🕐 Less than 10 minutes

Grey Divider

AI Description

• Add OpenPost as an official MCP server entry in the registry.
• Provide OAuth-enabled hosted Streamable HTTP installation endpoint.
• Include grounded prompt examples for scheduling, drafting, and status checks.
Diagram

graph TD
  Repo["MCP registry"] --> Manifest["openpost.json manifest"] --> Client("MCP client") --> Endpoint{{"OpenPost hosted MCP"}}

  subgraph Legend
    direction LR
    _repo["Registry/artifact"] ~~~ _cli("Client") ~~~ _ext{{"External endpoint"}}
  end
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Add a self-hosted installation option
  • ➕ Supports users who require on-prem/self-hosted deployment
  • ➕ Reduces reliance on hosted availability
  • ➖ Requires maintaining and documenting a deployable artifact (Docker image, Helm chart, etc.)
  • ➖ May increase support burden if deployments vary
2. Also publish a stdio/local runner installation
  • ➕ Works well for locked-down environments without outbound HTTP callbacks
  • ➕ Consistent local tooling story alongside other MCP servers
  • ➖ Not a fit if the server is designed around OAuth/web flows
  • ➖ Adds another distribution path to maintain

Recommendation: The PR’s approach (single recommended hosted Streamable HTTP installation with OAuth discovery plus examples) is the best default for an official server entry. Consider adding optional self-hosted or local/stdio installation blocks later if OpenPost supports and intends to maintain them.

Files changed (1) +57 / -0

Enhancement (1) +57 / -0
openpost.jsonAdd OpenPost server manifest with hosted HTTP install + examples +57/-0

Add OpenPost server manifest with hosted HTTP install + examples

• Introduces a new registry entry for the official OpenPost MCP server. Defines a recommended Streamable HTTP installation endpoint with OAuth discovery and includes several usage examples for scheduling, drafting, and status inspection.

mcp-registry/servers/openpost.json

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds a new MCP server manifest for OpenPost to the registry, using the registry’s HTTP installation type to point to OpenPost’s hosted, OAuth-enabled streamable HTTP endpoint, along with user-facing usage examples.

Changes:

  • Added openpost server entry with metadata (repo, homepage, author, license, categories/tags).
  • Declared a hosted http installation pointing to https://app.openpost.social/mcp and marked it as recommended.
  • Included several grounded prompt examples for common OpenPost workflows (review schedule, draft, schedule, status checks).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@mcp-registry/servers/openpost.json`:
- Line 14: Update the license metadata value in the OpenPost server definition
from AGPL-3.0 to the exact identifier AGPL-3.0-only, leaving the surrounding
metadata unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 437cd078-e636-491d-9622-ada6eea5aa84

📥 Commits

Reviewing files that changed from the base of the PR and between 6a92e54 and 84ee032.

📒 Files selected for processing (1)
  • mcp-registry/servers/openpost.json

Comment thread mcp-registry/servers/openpost.json Outdated
@qodo-code-review

Copy link
Copy Markdown
Contributor

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Qodo Logo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants