← Back to directory
S

SSE MCP Server Example

Community
An SSE MCP configuration example for hosted cloud services
GitHub source repository ↗
★ 32.6k Stars Category · Filesystem Very popular
26FMRS · D
Reliability
3/20
Security and permissions
6/20
Maintenance
8/20
Documentation
3/20
Setup experience
6/20

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.

Read the FMRS scoring method →

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.

Tools

The tool list has not been reviewed yet.

Setup

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.

claude_desktop_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}"}}}

Fit and risk

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

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

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

Supported clients

Supported clients have not been confirmed yet.

More servers from this repository