Remote HTTP MCP Server Examples
Copy common settings for popular hosted MCP servers, including GitHub, Supabase, Stripe, and Context7.
Use remote HTTP MCP servers when the provider hosts the server for you. In CloudCLI, add these from Settings > Configuration > Organization MCP, choose HTTP, then enter the URL and authentication settings.
For OAuth servers, create the server first, then click Connect in the Organization MCP list.
GitHub MCP
GitHub's hosted MCP server is useful for repository search, issues, pull requests, Actions, code security, and other GitHub workflows.
| Field | Value |
|---|---|
| Name | github |
| Transport | http |
| URL | https://api.githubcopilot.com/mcp/ |
| Auth mode | OAuth when supported, or static bearer token |
| Identity scope | Per-member for normal team use |
For static-token setups, add this header:
Authorization: Bearer <github-personal-access-token>Use the smallest GitHub token permissions that cover the tools you need. For organization-wide use, per-member OAuth or per-member tokens usually fit better than one shared admin token.
Supabase MCP
Supabase's remote MCP server can manage projects, query databases, inspect schemas, and work with Supabase platform features.
| Field | Value |
|---|---|
| Name | supabase |
| Transport | http |
| URL | https://mcp.supabase.com/mcp |
| Auth mode | OAuth |
| Identity scope | Per-member for most teams |
Recommended scoped URL:
https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=trueUse project_ref to keep the server focused on one Supabase project. Use read_only=true unless the agent should be allowed to make schema or data changes.
Stripe MCP
Stripe's remote MCP server supports Stripe API workflows through OAuth, and Stripe also documents a restricted API key fallback for clients that do not support OAuth.
| Field | Value |
|---|---|
| Name | stripe |
| Transport | http |
| URL | https://mcp.stripe.com |
| Auth mode | OAuth, or static bearer token with a restricted API key |
| Identity scope | Per-member for dashboard-user access; shared only for a deliberate service account workflow |
For restricted-key setups, add this header:
Authorization: Bearer <stripe-restricted-key>Prefer sandbox mode while testing. For live mode, use restricted keys that grant only the exact resources and actions the agent needs.
Context7 MCP
Context7 provides up-to-date library documentation to coding agents. It is a strong candidate for an organization MCP server because the same documentation lookup tool is useful in every environment.
| Field | Value |
|---|---|
| Name | context7 |
| Transport | http |
| URL | https://mcp.context7.com/mcp |
| Auth mode | Static headers |
| Identity scope | Not applicable |
Recommended header:
CONTEXT7_API_KEY: <context7-api-key>Context7 can be used without a key in some clients, but an API key is recommended for higher rate limits.
Security checklist
- Prefer OAuth or restricted tokens over broad secret keys.
- Use per-member OAuth when access should follow each user's provider permissions.
- Use shared OAuth only when the whole organization should act through one shared provider account.
- Scope provider URLs when supported, such as Supabase
project_refandread_only. - Rotate static tokens and remove servers that are no longer needed.
Official references
- GitHub MCP Server: https://github.com/github/github-mcp-server
- Supabase MCP Server: https://supabase.com/docs/guides/ai-tools/mcp
- Stripe MCP Server: https://docs.stripe.com/mcp
- Context7 MCP Server: https://github.com/upstash/context7