Add Taisly MCP server manifest

[taisly]

Adds a registry manifest for the official Taisly MCP server.

• Hosted Streamable HTTP transport with OAuth
• Local npm/stdio transport via @taisly/agent
• Current 13-tool surface
• MIT-licensed source and versioned npm package

The remote endpoint is live and returns the expected OAuth protected-resource challenge. The JSON manifest follows the registry schema and includes no undeclared placeholders.

Summary by CodeRabbit

• New Features
  • Added Taisly to the MCP server registry.
  • Included both hosted (OAuth-secured) and local installation options.
  • Documented supported MCP tools for authentication/setup, platform connectivity, post validation/creation, and repost automation.
  • Provided Taisly’s metadata, categories, tags, and marked it as official (not archived).

[coderabbitai]

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: 9c5e2129-1889-41a7-a476-0acb8dc491a8

📥 Commits

Reviewing files that changed from the base of the PR and between 7968bbc and 7eeb4f4.

📒 Files selected for processing (1)

• mcp-registry/servers/taisly.json

🚧 Files skipped from review as they are similar to previous changes (1)

• mcp-registry/servers/taisly.json

---

📝 Walkthrough

Walkthrough

Adds an official Taisly MCP server registry entry with metadata, hosted OAuth and local stdio installation methods, and declared tools for authentication, platform connections, posting, and repost automation.

Changes

Taisly MCP registration

Layer / File(s)	Summary
Taisly server metadata and installation registration mcp-registry/servers/taisly.json	Adds Taisly metadata, classifications, hosted HTTP and local npm/stdio installation targets, and its supported MCP tools.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 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 summarizes the main change: adding a Taisly MCP server manifest.
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

• X
• Mastodon
• Reddit
• LinkedIn

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

[qodo-code-review]

PR Summary by Qodo

Add Taisly MCP server manifest to registry

✨ Enhancement ⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Register the official Taisly MCP server in the registry.
• Document hosted HTTP+OAuth and local npm/stdio installation options.
• Enumerate the current tool surface and provide example prompts.

Diagram

graph TD
  R["MCP Registry"] --> M["taisly.json manifest"] --> H(["Hosted MCP (HTTP)"]) --> O{{"OAuth"}}
  M --> N["@taisly/agent (npm)"] --> L(["Local MCP (stdio)"])

  subgraph Legend
    direction LR
    _reg["Registry"] ~~~ _file["Manifest file"] ~~~ _svc(["Service"]) ~~~ _ext{{"External/Auth"}}
  end

Loading

High-Level Assessment

The PR’s approach—adding a single registry manifest that declares both hosted and local transports and enumerates tools/examples—is the right level of integration for a registry entry. The main review focus should be schema compliance (required fields, tool naming/description quality) and endpoint/package correctness, rather than architectural alternatives.

Files changed (1) +115 / -0

Other (1) +115 / -0

taisly.jsonAdd official Taisly MCP registry manifest (HTTP+OAuth and npm/stdio) +115/-0

Add official Taisly MCP registry manifest (HTTP+OAuth and npm/stdio)

• Introduces a new registry entry for the official Taisly MCP server, including repository/homepage metadata, licensing, and categorization. Declares two installation methods: a hosted HTTP endpoint protected by OAuth and a local npm/stdio transport via @taisly/agent. Lists the current tool surface and provides example prompts for publishing and auditing posts.

mcp-registry/servers/taisly.json

[Copilot]

Pull request overview

Adds a new MCP registry manifest for the official Taisly MCP server, enabling discovery and standardized configuration for both hosted (OAuth-protected) Streamable HTTP usage and local npx/stdio usage via @taisly/agent.

Changes:

• Added taisly server manifest with metadata (repository, homepage, author, license, categories, tags).
• Declared two installation methods: hosted Streamable HTTP endpoint and local npm (npx @taisly/agent mcp).
• Listed the current tool surface (13 tools) and included example prompts for common workflows.

---

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

[qodo-code-review]

Code Review by Qodo

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

Great, no issues found!

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

[coderabbitai]

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/taisly.json`:
- Around line 29-34: Update the installer’s recommended-method flow in the
install command to preserve selected_method.url for HTTP entries and configure
the hosted endpoint instead of retaining the fallback echo command. Ensure the
Taisly HTTP method can be auto-selected and installed using
https://app.taisly.com/mcp; alternatively remove its recommended flag until URL
handling is implemented.

🪄 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: 027a4b4d-4cb7-47c3-9c6c-27ba021c1bb5

📥 Commits

Reviewing files that changed from the base of the PR and between 6a92e54 and 7968bbc.

📒 Files selected for processing (1)

• mcp-registry/servers/taisly.json

[taisly]

Gentle follow-up: validate-manifests, tests, lint, and CodeRabbit are all green, and the single actionable bot finding was addressed. The PR is mergeable and only awaits maintainer review. Could someone take a look when convenient? Happy to make any further adjustments.