Best for
- Developers studying HTTP MCP configuration in Claude Code plugins
- API integrations that provide a compatible MCP HTTP endpoint and API_TOKEN
H
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.
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.
Tools
The tool list has not been reviewed yet.
Setup
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.
claude_desktop_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"}}}
Fit and risk
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
Troubleshooting
- Verify that API_TOKEN is supplied and that the Bearer format is correct
- Confirm that the HTTP URL points to an actual MCP endpoint rather than the example URL
- Check whether the target service requires the declared Content-Type, X-API-Version, or X-Service-Name headers
- Validate the JSON configuration and network access
- If used through a plugin, verify the plugin source and consult its homepage
Use cases
Reference for configuring an HTTP MCP connection to a REST API
Reference for using a Bearer API_TOKEN and custom request headers
Supported clients
Supported clients have not been confirmed yet.