Skip to content

Add RunAPI MCP server#75

Open
runapi-builder wants to merge 1 commit into
jmanhype:mainfrom
runapi-builder:codex/add-runapi-mcp
Open

Add RunAPI MCP server#75
runapi-builder wants to merge 1 commit into
jmanhype:mainfrom
runapi-builder:codex/add-runapi-mcp

Conversation

@runapi-builder

Copy link
Copy Markdown

Adds RunAPI MCP to the MCP Servers table.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Add RunAPI MCP server to README server list

📝 Documentation 🕐 Less than 5 minutes

Grey Divider

AI Description

• Add RunAPI MCP to the MCP Servers table.
• Document auth method (API key) and supported job types.
High-Level Assessment

The PR’s approach is optimal for the goal: add a single, consistent entry in the existing MCP Servers table. Alternatives (e.g., adding a separate section) would reduce discoverability and break the established format.

Files changed (1) +1 / -0

Documentation (1) +1 / -0
README.mdAdd RunAPI MCP row to MCP Servers table +1/-0

Add RunAPI MCP row to MCP Servers table

• Adds a new table entry for RunAPI MCP including its repository link, API key authentication method, and a short capability description (AI image/video/audio and LLM jobs).

README.md

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Grey Divider


Remediation recommended

1. Stale README status metrics 🐞 Bug ⚙ Maintainability
Description
After adding RunAPI MCP, the README Status table still reports "MCP servers | 5" (and "Last updated
| 2025-Q2"), which is now inaccurate relative to the updated MCP Servers list.
Code

README.md[42]

+| [RunAPI MCP](https://github.com/runapi-ai/mcp) | API key | AI image, video, audio, and LLM model jobs |
Evidence
The Status table claims there are 5 MCP servers and that the README was last updated in 2025-Q2, but
the MCP Servers table contains 6 rows including the newly added RunAPI entry.

README.md[7-13]
README.md[34-44]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The README "Status" summary is now inconsistent with the detailed "MCP Servers" table after adding a new server entry.

## Issue Context
A new MCP server row was added (RunAPI). The summary metrics at the top of the README should reflect the current list contents and the fact that the document was updated.

## Fix Focus Areas
- README.md[7-13]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

Comment thread README.md
| [GitHub MCP](https://github.com/modelcontextprotocol/servers/tree/main/src/github) | Token | Repos, issues, PRs, workflows |
| [Google Workspace MCP](https://github.com/aekanun2020/Google-MCP-Servers) | OAuth | Sheets, Drive, Gmail, Calendar, Docs, Slides, Tasks |
| [Notion MCP](https://www.notion.so/help/add-and-manage-connections-with-the-api#mcp) | OAuth | Notion workspaces |
| [RunAPI MCP](https://github.com/runapi-ai/mcp) | API key | AI image, video, audio, and LLM model jobs |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remediation recommended

1. Stale readme status metrics 🐞 Bug ⚙ Maintainability

After adding RunAPI MCP, the README Status table still reports "MCP servers | 5" (and "Last updated
| 2025-Q2"), which is now inaccurate relative to the updated MCP Servers list.
Agent Prompt
## Issue description
The README "Status" summary is now inconsistent with the detailed "MCP Servers" table after adding a new server entry.

## Issue Context
A new MCP server row was added (RunAPI). The summary metrics at the top of the README should reflect the current list contents and the fact that the document was updated.

## Fix Focus Areas
- README.md[7-13]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

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.

1 participant