typestrict.aidocs

Other assistants

Zed, Kiro, opencode, Cline and any MCP client with typestrict.

Any MCP client works with the remote server, https://api.typestrict.ai/mcp (streamable HTTP, OAuth or an API key in Authorization: Bearer ts_...), or with the local one, the command typestrict mcp over stdio.

Zed (settings.json)
{ "context_servers": { "typestrict": { "url": "https://api.typestrict.ai/mcp" } } }
Kiro (.kiro/settings/mcp.json)
{ "mcpServers": { "typestrict": { "url": "https://api.typestrict.ai/mcp" } } }
opencode (opencode.json)
{ "mcp": { "typestrict": { "type": "remote", "url": "https://api.typestrict.ai/mcp" } } }

Sign in with opencode mcp auth typestrict.

Cline (MCP settings)
{ "mcpServers": { "typestrict": { "type": "streamableHttp", "url": "https://api.typestrict.ai/mcp" } } }

Skills. Most assistants read the open skills format from .agents/skills; see typestrict-lab/skills.

For client developers. The server publishes its metadata at https://api.typestrict.ai/.well-known/oauth-protected-resource/mcp (RFC 9728) and answers a request without a token with a 401 pointing at it. The authorization server is https://typestrict.ai: PKCE (S256), the resource parameter (RFC 8707), Client ID Metadata Documents or dynamic client registration, and the iss parameter on the redirect (RFC 9207).