Shared service (SSE)
Connect to a service your team already runs. For an older service that streams over SSE, on /sse and /messages.
What you will be asked for
- Address
- Authorization headerSecret
- Other header
- Its valueSecret
Where to find these
Connects any service that speaks the standard tool protocol over SSE: an internal tool, a vendor's endpoint, or something your team wrote.
Service URL
The service endpoint, usually ending in /sse:
https://tools.internal.example.com/sse
Whoever operates the service has this. If they give you an address ending in
/mcp, use the plain Shared service template instead. The two are not
interchangeable.
Authorization
Most services want one of:
- Bearer token: put the token in the
authorizationfield and Worclaude sendsAuthorization: Bearer <token>. - A custom header: some services use
X-API-Keyor similar. Put the header name inheader_nameand the value inheader_value.
Leave all three blank for a service that needs no authentication, which is reasonable only on a private network.
Getting a token
There is no single answer, it depends on the service. Ask whoever runs it for a read-only token scoped to what you actually need. The model can call every tool the service exposes, so the token's permissions are the real boundary, not anything configured here.
About a minute, once you have the credentials.