Skip to content

feat(mcp): add PlanetScale and OpenRouter servers - #192

Merged
shunkakinoki merged 1 commit into
mainfrom
codex/add-planetscale-openrouter-mcp
Aug 10, 2026
Merged

shunkakinoki merged 1 commit into
mainfrom
codex/add-planetscale-openrouter-mcp

Conversation

@shunkakinoki

@shunkakinoki shunkakinoki commented Aug 10, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • add the hosted PlanetScale MCP server
  • add the hosted OpenRouter MCP server

Both entries use the official HTTP endpoints and inherit OAuth authentication from the MCP clients.

Validation

  • jq empty .ruler/mcp.json
  • git diff --check

Summary by cubic

Added hosted PlanetScale and OpenRouter MCP servers to .ruler/mcp.json. They use official HTTP endpoints and reuse OAuth from existing MCP clients.

Written for commit 01e460f. Summary will update on new commits.

Review in cubic

@coderabbitai

coderabbitai Bot commented Aug 10, 2026 •

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Expanded internal service connectivity to support additional integrations.
    • No changes to the user interface or existing application behavior.

Walkthrough

The MCP configuration adds HTTP server entries for OpenRouter and PlanetScale alongside the existing Paybox server.

Changes

MCP server configuration

Layer / File(s) Summary
Add remote MCP servers
.ruler/mcp.json
The configuration adds HTTP endpoints for OpenRouter and PlanetScale under mcpServers.

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

Possibly related PRs

Poem

A rabbit hops through config lines,
Two MCP paths now neatly shine.
OpenRouter joins the queue,
PlanetScale arrives there too.
“Hop!” says the bunny, “Clean and bright!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely identifies the addition of the PlanetScale and OpenRouter MCP servers.
Description check ✅ Passed The description accurately explains the configuration changes, endpoints, authentication, and validation performed.
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
  • Commit unit tests in branch codex/add-planetscale-openrouter-mcp

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.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

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 @.ruler/mcp.json:
- Around line 28-29: Align the HTTP MCP discriminator across `.ruler/mcp.json`,
`skills/create-plugin/SKILL.md`, and all `mcp-sync` targets by adopting one
supported field consistently. Update the sync logic and validation to preserve
that field, or explicitly translate between the documented `transport` form and
each target’s required format; ensure Codex receives a valid `mcp.json` entry.
🪄 Autofix

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2f4f97fc-a55d-4119-b444-f260870981e1

📥 Commits

Reviewing files that changed from the base of the PR and between 6caee97 and 01e460f.

📒 Files selected for processing (1)
  • .ruler/mcp.json

Comment thread .ruler/mcp.json
Comment on lines +28 to +29
"type": "http",
"url": "https://mcp.openrouter.ai/mcp"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -n -C 4 \
  '"(type|transport)"[[:space:]]*:[[:space:]]*"http"|MCP_TARGET_DIRS|MCP_SETTINGS_TARGETS|enabledMcpjsonServers' \
  .ruler/mcp.json Makefile skills/create-plugin/SKILL.md

Repository: shunkakinoki/dotagents

Length of output: 3003


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== relevant docs =="
sed -n '1,220p' skills/create-plugin/SKILL.md | grep -n -C 5 -E '"transport"|"type"|"mcpServers"|HTTP|mcp' || true

echo
echo "== all occurrences =="
rg -n -C 2 \
  '"(type|transport)"[[:space:]]*:[[:space:]]*"http"|transport.*http|type.*http|mcpServers|enabledMcpjsonServers' \
  .ruler/mcp.json Makefile skills/create-plugin/SKILL.md $(git rev-parse --show-toplevel)

Repository: shunkakinoki/dotagents

Length of output: 11066


🌐 Web query:

OpenRouter MCP HTTP transport field type transport mcp.json schema "mcp.openrouter.ai/mcp"

💡 Result:

The OpenRouter MCP server, located at https://mcp.openrouter.ai/mcp, is configured as a remote HTTP-based MCP server [1][2]. In the Model Context Protocol (MCP) configuration file (mcp.json), remote servers do not use a transport field type; instead, they are identified by the use of the url property [3]. When configuring OpenRouter in your mcp.json file, you should define it as follows [1][2]: { "mcpServers": { "openrouter": { "url": "https://mcp.openrouter.ai/mcp" } } } Key details regarding this configuration include: 1. Transport Mechanism: While some MCP clients allow you to explicitly define the transport type (e.g., specifying type: "http" or type: "remote" for clarity) [1][4], the core requirement for connecting to OpenRouter is the presence of the url field pointing to the specified endpoint [3]. 2. Authentication: The server uses an OAuth-based flow [1][5]. When an unauthenticated request is made to the endpoint, the server returns a 401 status code, which triggers the client to initiate the OpenRouter OAuth authorization flow [1][5]. Once authorized, the client receives an API key that is subsequently used for authenticated requests [1][5]. 3. Configuration Flexibility: Depending on the specific MCP client (such as Claude Desktop, Cursor, or custom implementations), you may place this configuration in your global mcp.json file or add it via the client's built-in connector interface [1][2][3]. If your client specifically requires a type field to distinguish between local (stdio) and remote (http) servers, http is the correct designation [4][6].

Citations:


🌐 Web query:

Claude Desktop mcp.json remote HTTP transport type http url

💡 Result:

Claude Desktop does not natively support the HTTP transport configuration ("type": "http" with a "url") in its claude_desktop_config.json file [1][2]. If you attempt to use this configuration, Claude Desktop will likely ignore the entry, fail to load it, or in some cases, silently strip the server configuration from your file [3][1][2]. To connect to remote HTTP-based MCP servers in Claude Desktop, you should use one of the following two approaches: 1. Custom Connectors (Recommended for public services): For remote, internet-accessible HTTP MCP servers (typically with OAuth or API key authentication), use the Custom Connectors feature in Claude Desktop settings [1][4]. This allows Claude's cloud infrastructure to connect directly to your remote server [4]. 2. Local Stdio-to-HTTP Bridge (Recommended for local HTTP servers): If you must connect to a local HTTP server (e.g., http://127.0.0.1:8080/mcp), you can use a stdio-based proxy such as mcp-remote [1][2]. In this setup, you configure Claude Desktop to run mcp-remote as a standard stdio process, and the proxy handles the HTTP communication with your server [1][2]. Example configuration for using the stdio-to-HTTP bridge in claude_desktop_config.json: { "mcpServers": { "my-local-http-server": { "command": "npx", "args": [ "-y", "mcp-remote", "http://127.0.0.1:8080/mcp", "--transport", "http-only" ] } } } Note: The type: "http" configuration format is supported by other MCP clients, such as Claude Code (via .mcp.json or ~/.claude.json), but it is distinct from Claude Desktop's local configuration requirements [5][2][6]. Always ensure your MCP server is configured to use the "Streamable HTTP" transport, which is the current standard for HTTP-based MCP communication [7][8][9].

Citations:


🌐 Web query:

Cursor .cursor mcp.json mcpServers transport type url

💡 Result:

In Cursor, the configuration of MCP servers is handled within a mcp.json file, which can be located either at .cursor/mcp.json (for project-specific settings) or ~/.cursor/mcp.json (for global settings) [1][2][3]. The configuration schema distinguishes between two primary transport methods: local (stdio) and remote (HTTP-based) [4][5]. Local Servers (stdio) To configure a local server, you define it using the command field [1][2]. The type field is typically "stdio" (though often inferred if command is present) [2][6]. { "mcpServers": { "my-local-server": { "command": "npx", "args": ["-y", "mcp-server"], "env": { "API_KEY": "value" } } } } Remote Servers (URL) For remote servers, you use the url field instead of command [1][2][3]. While the official Cursor documentation often demonstrates these without an explicit type field, some implementations or related client tools use type to specify the HTTP transport (e.g., "http" or "sse") [2][5]. { "mcpServers": { "my-remote-server": { "url": "https://mcp.example.com/mcp", "headers": { "Authorization": "Bearer your-token-here" } } } } Key Configuration Notes: - Transport Types: The Model Context Protocol (MCP) officially defines stdio and Streamable HTTP as the current standard transports [7][8][5]. Older HTTP+SSE configurations are considered legacy/deprecated [5]. - Variable Resolution: Cursor supports variable resolution (e.g., ${env:VAR_NAME} or ${workspaceFolder}) within command, args, env, url, and headers fields [2][6]. - Priority: If the same server name exists in both project-level and global configuration files, the project-level settings take precedence [1]. - Security: Never hard-code sensitive API keys or secrets directly in your configuration; use environment variables or environment files (envFile) instead [2][3][4].

Citations:


🌐 Web query:

Codex /kilo .codex mcp.json mcpServers transport type url

💡 Result:

The configuration format for Model Context Protocol (MCP) servers varies depending on the specific tool or environment (e.g., Kilo Code/Kilocode, Codex, or VS Code), though most follow a similar pattern of nesting servers under an mcpServers object within a JSON configuration file [1][2][3][4]. Configuration Summary: 1. Codex: Codex primarily uses a TOML-based configuration file located at ~/.codex/config.toml, where servers are defined under an [mcp_servers.] table [5][6]. However, when using JSON configuration (such as in plugins or project-specific files), it expects the mcpServers wrapper [4]. For URL-based (remote) servers, the transport type is typically identified as streamable_http [7][6]. 2. Kilo Code (Kilocode): Kilo Code configurations are managed in files such as kilo.json or mcp.json [1][3]. The structure uses an mcpServers object where each server defines a type (e.g., local or remote) [1][8]. For remote servers, you must provide a url and optional headers [1][3]. 3. General Structure (.mcp.json): In many implementations, the mcp.json file serves as the standard configuration file [9][10]. The typical structure is: { "mcpServers": { "my-server-name": { "type": "remote", "url": "https://example.com/mcp", "headers": { "Authorization": "Bearer " } } } } Key Transport Considerations: - Transport Types: Common values for the type field include local (or stdio), remote, streamable_http, and sse [1][3][9][10][11]. - URL Requirement: When the type is set to remote, streamable_http, or sse, the url field is strictly required to define the server endpoint [3][6][9][10][11]. - Compatibility: Always check your specific tool's documentation, as some clients (like Claude Code or specific versions of Codex) may strictly require the mcpServers wrapper, while others might support flat configurations [4][12][10][11].

Citations:


🌐 Web query:

"OpenRouter MCP server" "mcp.openrouter.ai/mcp" Claude Code type http

💡 Result:

The OpenRouter MCP server, located at https://mcp.openrouter.ai/mcp, is a remote server that allows your AI tools to access live OpenRouter data, such as model catalogs, pricing, benchmark rankings, and your account credits [1][2]. It uses the HTTP transport protocol [1][3]. To connect the OpenRouter MCP server to a client (such as Claude Desktop or other MCP-compatible tools), you generally add the server URL and then perform an OAuth login [1][2]. For example, in command-line environments, you can typically use: claude mcp add --transport http openrouter https://mcp.openrouter.ai/mcp claude mcp login openrouter In JSON configuration files, it is structured as: { "mcpServers": { "openrouter": { "type": "http", "url": "https://mcp.openrouter.ai/mcp" } } } Note that Claude Code itself integrates with OpenRouter primarily by routing the Anthropic API calls to OpenRouter's "Anthropic Skin" (via setting the ANTHROPIC_BASE_URL to https://openrouter.ai/api), rather than connecting to OpenRouter via an MCP server [4]. The OpenRouter MCP server is intended to be used as a tool provider for your agents, allowing them to search for models or check your usage [2][5]. Using the OpenRouter MCP server provides your agent with real-time data to help it decide which model to use, whereas the "Anthropic Skin" configuration allows the agent to actually execute tasks using OpenRouter's infrastructure [2][4].

Citations:


🌐 Web query:

Claude Code MCP configuration transport type http mcpServers type

💡 Result:

In Claude Code, when configuring an MCP server that uses HTTP transport, the type field in your configuration must be set to "http" [1][2]. While the broader Model Context Protocol (MCP) specification defines a "Streamable HTTP" transport [2], Claude Code specifically requires the literal string "http" for its configuration schema [1][2]. Using other identifiers—such as "streamable-http"—will result in a configuration error [2]. Configuration Details: - Transport Type: "type": "http" [1][3] - Required Field: "url" (the endpoint of your MCP server) [1][4] - Optional Field: "headers" (for authentication tokens or custom headers) [1][5][3] Example JSON Configuration: { "mcpServers": { "your-server-name": { "type": "http", "url": "https://api.example.com/mcp", "headers": { "Authorization": "Bearer YOUR_TOKEN" } } } } You can manage these configurations via the command line using claude mcp add --transport http <name> <url> [1][4], or by manually editing your configuration files (.mcp.json or ~/.claude.json) [1][5]. Note that the older SSE (Server-Sent Events) transport is deprecated in favor of this HTTP transport [1][5].

Citations:


Use HTTP-compatible entries for each shared sync target.

.ruler/mcp.json, skills/create-plugin/SKILL.md, and the synced targets do not agree on one HTTP discriminator: transport: "http" is documented, but the synced entries use type: "http". Codex does not reliably accept this mcp.json format. Either move HTTP MCPs out of these shared configs, switch all targets to a common supported field, or add and validate explicit translation during mcp-sync.

🧰 Tools
🪛 SkillSpector (2.5.1)

[warning] 20: [E1] External Transmission: Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Remediation: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

(Data Exfiltration (E1))


[warning] 33: [E1] External Transmission: Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Remediation: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

(Data Exfiltration (E1))

🤖 Prompt for 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.

In @.ruler/mcp.json around lines 28 - 29, Align the HTTP MCP discriminator
across `.ruler/mcp.json`, `skills/create-plugin/SKILL.md`, and all `mcp-sync`
targets by adopting one supported field consistently. Update the sync logic and
validation to preserve that field, or explicitly translate between the
documented `transport` form and each target’s required format; ensure Codex
receives a valid `mcp.json` entry.

@shunkakinoki
shunkakinoki merged commit 8bfa674 into main Aug 10, 2026
4 checks passed
@shunkakinoki
shunkakinoki deleted the codex/add-planetscale-openrouter-mcp branch August 10, 2026 10:28
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