Hosted MCP server/Cloud Service

Shipvela MCP server

Hosted at shipvela.com·Streamable HTTP

Shipvela deploys GitHub projects from an MCP client, inspects build logs, and returns live URLs. The hosted server uses Streamable HTTP with OAuth: run codex mcp add shipvela --url https://shipvela.com/mcp, then codex mcp login shipvela and restart. Local prebuilt sites can be published in chat when under 500 KB and 100 files with a root index.html and no compilation; the separately authenticated CLI handles larger output folders and build steps. The GitHub-repository publishing workflow comes from the Shipvela plugin, not the bare endpoint.

shipvela.com Streamable HTTP OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Teams that deploy GitHub projects through an MCP client and want build log inspection and live URL retrieval.

  • Add the server and run codex mcp login shipvela.
  • Publish a small prebuilt site in chat.
  • Add the plugin for GitHub-repository publishing.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Codex setup

Then run codex mcp login shipvela and restart Codex. For the full GitHub-repository publishing workflow, add the plugin: codex plugin marketplace add stefanautomateed/shipvela-codex and codex plugin add shipvela@shipvela-beta.

  1. Add the MCP server

    Register the hosted Shipvela server in Codex.

    codex mcp add shipvela --url https://shipvela.com/mcp
  2. Sign in

    Complete OAuth for the Shipvela server, then restart Codex.

    codex mcp login shipvela
  3. Add the plugin

    The plugin supplies the GitHub-repository publishing workflow.

    codex plugin marketplace add stefanautomateed/shipvela-codex

Follow the provider's setup steps above, then connect the server in your client. The provider controls the endpoint, required credentials, and permissions.

Connection

Endpoint and configuration

Endpoint
https://shipvela.com/mcp
Host
shipvela.com · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
shipvela
Listing type
Community or directory listing

The installer uses the server name shipvela. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that shipvela appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Add the server and run codex mcp login shipvela. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Shipvela documentationhttps://shipvela.com/integrations/codexGitHub repositoryhttps://github.com/stefanautomateed/shipvela-codex