mirror of
https://github.com/coder/coder.git
synced 2026-09-21 12:44:32 +08:00
chore: retire mark3labs/mcp-go dependency (#28061)
## Stack Context PR 6 of 6 in a stack that migrates every Coder MCP surface from the archived `github.com/mark3labs/mcp-go` library to the official `github.com/modelcontextprotocol/go-sdk` v1.7.0. Stack: #28056 -> #28057 -> #28058 -> #28059 -> #28060 -> #28061 ## Why With every production surface migrated, this PR removes the mark3labs dependency entirely and converts the remaining test fixtures. - Migrates the remaining mark3labs test fixtures (coderd MCP e2e tests, chatd fixtures, mcpclient fixtures, and the Force On MCP policy tests) to official stateless SDK servers. - Removes `github.com/mark3labs/mcp-go` from `go.mod` and drops the corresponding dependabot ignore entry. Zero references remain repo-wide. - Updates the MCP docs for the 2026-07-28 protocol: stateless Streamable HTTP behavior, the supported 2024-11-05 through 2026-07-28 protocol range, and explicit non-features (resources, prompts, structured output, elicitation, MCP Tasks). - The e2e ping assertion is removed because MCP 2026-07-28 removed the ping method. > Mux created this PR on Mike's behalf.
This commit is contained in:
@@ -19,7 +19,7 @@ AI Gateway can connect to MCP servers and inject tools automatically, enabling y
|
||||
> [!NOTE]
|
||||
> Only MCP servers which support OAuth2 Authorization are supported currently.
|
||||
>
|
||||
> [_Streamable HTTP_](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#streamable-http) is the only supported transport currently. In future releases we will support the (now deprecated) [_Server-Sent Events_](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#backwards-compatibility) transport.
|
||||
> [_Streamable HTTP_](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports) is the only supported transport currently. In future releases we will support the (now deprecated) [_Server-Sent Events_](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports#backwards-compatibility) transport.
|
||||
|
||||
AI Gateway makes use of [External Auth](../../admin/external-auth/index.md) applications, as they define OAuth2 connections to upstream services. If your External Auth application hosts a remote MCP server, you can configure AI Gateway to connect to it, retrieve its tools and inject them into requests automatically - all while using each individual user's access token.
|
||||
|
||||
|
||||
@@ -87,6 +87,16 @@ The remote MCP server is an HTTP endpoint exposed by your Coder deployment at
|
||||
`/api/experimental/mcp/http`. This enables MCP clients to connect to Coder
|
||||
without running the CLI locally.
|
||||
|
||||
The endpoint implements the
|
||||
[Streamable HTTP transport](https://modelcontextprotocol.io/specification/2026-07-28/basic/transports)
|
||||
in stateless mode: it supports MCP specification versions from `2024-11-05`
|
||||
through `2026-07-28`, does not issue `Mcp-Session-Id` headers, and answers
|
||||
`GET` and `DELETE` with `405 Method Not Allowed` (there is no standalone
|
||||
server-event stream or explicit session termination, both permitted by the
|
||||
specification). The server exposes tools only; MCP resources, prompts,
|
||||
structured tool output, elicitation, and the MCP Tasks extension (which is
|
||||
unrelated to Coder's task tools) are not implemented.
|
||||
|
||||
### Prerequisites
|
||||
|
||||
The remote MCP HTTP endpoint requires both the `oauth2` and `mcp-server-http`
|
||||
|
||||
Reference in New Issue
Block a user