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

SSE MCP Server Example

Community
Tutorial / collection
An SSE MCP configuration example for hosted cloud services

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

How to install ↓ Compare GitHub source repository ↗
Category
Filesystem #24 of 24
Stars
★ 42.7k Very popular
Transport
SSE
Runtime
Hosted (no local runtime)
Credentials
Optional API key
License
Apache-2.0
Last commit
26FMRS · D

This source file is an SSE configuration example for hosted cloud services, not a product-specific tool catalog. It lists Asana, GitHub, and an example custom-service endpoint, but provides no evidence about tools, permissions, authentication flow, or client compatibility.

Strongest · Maintenance 8/20 Weakest · Reliability 3/20

Reliability
3/20
Security and permissions
6/20
Maintenance
8/20
Documentation
3/20
Setup experience
6/20
Why each score
Reliability 3/20
The file is only a configuration example containing three remote SSE endpoints. It provides no server implementation, initialization handshake, tool list, error handling, dependency information, tests, or CI evidence; custom-service is also a placeholder endpoint. The configuration shape is plausible, but actual startup and tool behavior are unverifiable, so substantial points are deducted.
Security and permissions 6/20
The configuration connects to external Asana, GitHub, and custom services, and uses environment variables for custom-service client headers. It does not document authentication, credential protection, permission scope, data boundaries, transport-security details, or confirmation for dangerous operations. No explicit red-line risk is shown, but evidence for least privilege and control is insufficient, warranting a low score.
Maintenance 8/20
The repository is described as an Anthropic-managed official directory, is not archived, and states an Apache-2.0 license, providing positive ownership and licensing evidence. However, the supplied material contains no release history, commit activity, issue-response evidence, dependency-update process, or security-response channel, so a high score is not justified.
Documentation 3/20
The README mainly documents the plugin directory structure, installation command, and general plugin guidance. It does not document this SSE configuration's authentication, tool parameters, capabilities, limits, costs, troubleshooting, or service availability. It also states that included MCP servers cannot be verified, leaving weak reviewable evidence for this server.
Setup experience 6/20
The manifest gives a usable configuration shape, service names, SSE URLs, and an environment-variable example, so it offers some setup guidance. It lacks runtime preparation, complete mainstream-client connection steps, authentication instructions, platform compatibility, and a real custom-service endpoint. The example therefore cannot establish a directly working connection and receives only a below-average score.

Test out of dateListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the network

Best for

  • Claude Code plugin developers looking for an SSE MCP configuration example
  • Users who know and trust the configured cloud-service endpoints

Not for

  • Users who require a documented tool inventory
  • Users who require verified permission scopes or client compatibility
  • Users who do not trust the configured external endpoints

Required permissions

  • The configuration indicates access to the listed SSE endpoints, but specifies no account permissions or authorization scopes
  • custom-service includes the X-API-Version: v1 header and an X-Client-ID header using ${CLIENT_ID}

Risks and side effects

  • The README warns that MCP servers, files, or software included in plugins are not controlled or verified by Anthropic
  • The source does not verify endpoint behavior, availability, or permission requirements
  • Sending header values to an untrusted service may expose information

Setup

Before you start

Runtime：Hosted (no local runtime)

Other optional settings (1)
CLIENT_ID optional Client identifier used in the example config's X-Client-ID header for the custom service; obtain it from the provider of the service you connect to.

The README states that plugins can be installed through Claude Code with /plugin install {plugin-name}@claude-plugins-official or discovered through /plugin > Discover. This configuration is located at plugins/plugin-dev/skills/mcp-integration/examples/sse-server.json. Before use, verify each service URL and provide CLIENT_ID for custom-service if required by that service.

MCP config · JSON 
{"asana":{"type":"sse","url":"https://mcp.asana.com/sse"},"github":{"type":"sse","url":"https://mcp.github.com/sse"},"custom-service":{"type":"sse","url":"https://mcp.example.com/sse","headers":{"X-API-Version":"v1","X-Client-ID":"${CLIENT_ID}"}}}

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
{
  "asana": {
    "type": "sse",
    "url": "https://mcp.asana.com/sse"
  },
  "github": {
    "type": "sse",
    "url": "https://mcp.github.com/sse"
  },
  "custom-service": {
    "type": "sse",
    "url": "https://mcp.example.com/sse",
    "headers": {
      "X-API-Version": "v1",
      "X-Client-ID": "${CLIENT_ID}"
    }
  }
}

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

Generate and validate client config

Check that it works

Add the SSE server entries to your Claude Code MCP config, restart the client, and check that Asana or GitHub tools appear in the tool list to confirm the connection works.

Troubleshooting

  1. Confirm that the SSE URLs exactly match the configuration
  2. Confirm that the target service supports SSE MCP connections
  3. Check whether custom-service can resolve CLIENT_ID and verify the header names and values
  4. Confirm that the containing plugin was installed through Claude Code's plugin system

Things to try

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

  • List my open tasks in Asana
  • Show my most recent open pull requests on GitHub
  • Query the custom SSE service with my client ID header

Use cases

Connecting to a hosted Asana service over SSE
Connecting to a hosted GitHub service over SSE
Configuring a custom SSE service with request headers

Overview

An example SSE MCP configuration for hosted cloud services, defining SSE connections for Asana, GitHub, and custom-service. The source does not list specific tools, tool descriptions, client compatibility, or service permission scopes.

Similar servers

Compare with other MCP servers

More servers from this repository

HTTP MCP ServerFilesystem MCP Server

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