M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
H

HTTP MCP Server

Community
Tutorial / collection
HTTP MCP configuration example for REST APIs

This is a tutorial or resource collection; there is nothing to install into a client.

How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #380 of 438
Stars
★ 42.7k Very popular
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
Apache-2.0
Last commit
36FMRS · D

The source establishes this as an HTTP MCP configuration example in an Anthropic-managed directory, but not as a directly usable production server. It provides no tool list, client compatibility information, or verified service capabilities.

Strongest · Maintenance 11/20 Weakest · Documentation 4/20

Reliability
5/20
Security and permissions
8/20
Maintenance
11/20
Documentation
4/20
Setup experience
8/20
Why each score
Reliability 5/20
The file only provides two HTTP MCP configuration entries. It contains no declared tools, initialization/tool-list handshake evidence, tests, timeouts, retries, or error handling. HTTPS and an environment-variable token make the happy path plausible, but the source cannot verify service availability or behavioral consistency, so substantial points are deducted.
Security and permissions 8/20
The configuration uses HTTPS and references credentials through ${API_TOKEN}; no real token is exposed. However, token scopes, API permissions, data boundaries, logging behavior, and confirmation for potentially risky operations are undocumented. No explicit red-line risk is shown, but the absence of least-privilege and data-flow evidence warrants deductions.
Maintenance 11/20
The repository is identified as Anthropic-managed, is not archived, and states an Apache-2.0 license, providing reasonably clear ownership and licensing. The source material provides no release history, commit activity, dependency-update process, issue-response evidence, or security-response channel. Stars and open-issue counts do not add points, so this receives a moderate score.
Documentation 4/20
The README primarily documents the general plugin directory, structure, and installation flow. It does not document this HTTP configuration's tool parameters, authentication preparation, limits, costs, troubleshooting, or service availability. The manifest example is mildly useful, but server-specific documentation is largely absent.
Setup experience 8/20
The manifest shows URLs, headers, and an environment-variable token, and an HTTP service theoretically requires no local runtime. However, it lacks complete mainstream-client configuration steps, environment preparation, platform compatibility details, and connection verification, leaving setup incomplete.

Test out of dateListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Developers studying HTTP MCP configuration in Claude Code plugins
  • API integrations that provide a compatible MCP HTTP endpoint and API_TOKEN

Not for

  • Users seeking a verified production service
  • Users needing a documented tool list, concrete API capabilities, or client compatibility
  • Users expecting the example api.example.com endpoint to provide a working business service

Required permissions

  • Network access to the configured HTTP endpoint
  • An API_TOKEN environment variable or equivalent Bearer credential
  • Permission for requests to use the declared Content-Type, API version, and service-name headers

Risks and side effects

  • api.example.com/mcp is an example URL; the source does not establish that it is operational or belongs to a real service
  • API_TOKEN is sensitive authentication material and should not be exposed in untrusted configuration or logs
  • The README warns users to trust plugins before installing, updating, or using them; Anthropic does not control the MCP servers included in plugins and cannot verify that they work as intended or remain unchanged

Setup

Before you start

Runtime：Hosted (no local runtime)

API_TOKEN requiredsecret Bearer token used in the Authorization header of HTTP requests; obtain it from the operator of the target API (api.example.com).

The source provides no dedicated installation steps for this example server. The configuration requires an HTTP URL, a Bearer API_TOKEN, and the relevant request headers. The README states that plugins can be installed with /plugin install {plugin-name}@claude-plugins-official, but it does not explain how to install this example server separately.

MCP config · JSON 
{"rest-api":{"type":"http","url":"https://api.example.com/mcp","headers":{"Authorization":"Bearer ${API_TOKEN}","Content-Type":"application/json","X-API-Version":"2024-01-01"}},"internal-service":{"type":"http","url":"https://api.example.com/mcp","headers":{"Authorization":"Bearer ${API_TOKEN}","X-Service-Name":"claude-plugin"}}}

Works in clients that read an "mcpServers" key. For clients such as VS Code that use a different key, the configurator below converts it.

.vscode/mcp.json
{
  "rest-api": {
    "type": "http",
    "url": "https://api.example.com/mcp",
    "headers": {
      "Authorization": "Bearer ${API_TOKEN}",
      "Content-Type": "application/json",
      "X-API-Version": "2024-01-01"
    }
  },
  "internal-service": {
    "type": "http",
    "url": "https://api.example.com/mcp",
    "headers": {
      "Authorization": "Bearer ${API_TOKEN}",
      "X-Service-Name": "claude-plugin"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Generate and validate client config

Check that it works

After installing a plugin with this .mcp., check that the rest-api and internal-service HTTP servers appear as connected in your client's MCP server list to confirm the configuration loaded.

Troubleshooting

  1. Verify that API_TOKEN is supplied and that the Bearer format is correct
  2. Confirm that the HTTP URL points to an actual MCP endpoint rather than the example URL
  3. Check whether the target service requires the declared Content-Type, X-API-Version, or X-Service-Name headers
  4. Validate the JSON configuration and network access
  5. If used through a plugin, verify the plugin source and consult its homepage

Things to try

Once connected, you can ask your AI assistant things like:

  • Call the REST API through the rest-api server and show me the response
  • Send a request via the internal-service server and summarize the result

Use cases

Reference for configuring an HTTP MCP connection to a REST API
Reference for using a Bearer API_TOKEN and custom request headers

Overview

This is an HTTP MCP server configuration example in Anthropic's official Claude Code Plugins Directory, located under the mcp-integration skill examples. It defines two HTTP entries, rest-api and internal-service, both targeting the example URL https://api.example.com/mcp. The source lists no tools, so its available tools and operational capabilities cannot be confirmed.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 63.3k · Tools 2 Compare with this →
Compare with other MCP servers

More servers from this repository

SSE MCP Server ExampleFilesystem MCP Server

Source revision ea10b213686c Data synced 2026-10-19 Read the FMRS scoring method