MCP servers

Tasuku supports remote MCP servers over HTTPS. Codex and OpenCode support Streamable HTTP servers. Claude supports Streamable HTTP and legacy SSE servers. Tasuku rejects legacy SSE when Codex or OpenCode is selected instead of generating an unusable runtime configuration.

{
  "name": "linear",
  "transport": "HTTP",
  "url": "https://mcp.example.com/mcp",
  "headers": [
    { "name": "Authorization", "value": "Bearer ${secrets.LINEAR_TOKEN}" }
  ]
}

Header secrets

Header values may reference separately stored secrets. The configuration retains the reference; Tasuku resolves it for the invocation without returning the plaintext through read APIs.

A repository secret with the same name shadows the organization secret for that repository. This lets one shared MCP definition use repository-specific credentials.

Names and URLs

Server names must match ^[a-z0-9][a-z0-9_-]*$ and be unique. Two names are reserved: composio for connected apps and tasuku_repository_context for the built-in repository-context server. URLs must be HTTPS and must not contain user info.

Provider mapping

Tasuku converts the same logical MCP server into provider-specific Codex, Claude, or OpenCode invocation configuration.

Safety

Only add servers you trust with the repository context the agent may send. HTTPS protects transport, but it does not make the remote service an internal Tasuku component. Review its retention, authorization, and tenant boundaries separately.

Local, plaintext HTTP, and arbitrary stdio transports are not accepted by the current configuration API.