Sanka Server

This repository contains the hosted Sanka MCP service and the internal TypeScript API client it depends on. It is now maintained as a normal TypeScript workspace, not as a Stainless-managed repository.

The production service is a remote Streamable HTTP MCP endpoint:

• POST /mcp as the primary endpoint
• POST /sse as a compatibility alias for clients that still expect an SSE-style path
• POST / as a compatibility alias
• GET /health for health checks

The /mcp endpoint exposes both the general SDK tools and the read-only CRM tools from a single MCP surface.

Live endpoints:

• https://mcp.sanka.com/mcp
• https://mcp.sanka.com/sse

Staging endpoint:

• https://sanka-mcp-staging.fly.dev/mcp

Repository layout

• src/: internal Sanka API client used by the MCP service
• packages/mcp-server/: the MCP server application and Docker entrypoint
• .github/workflows/: CI plus staging and production Fly deployment workflows
• fly.toml: production Fly app configuration
• fly.staging.toml: staging Fly app configuration
• docs/openapi-maintenance.md: guidance for keeping API coverage current without Stainless

Auth

Remote clients authenticate with either:

• Authorization: Bearer <token>
• x-sanka-api-key: <token>

The server forwards those credentials to the Sanka public API.

Local development

pnpm install
pnpm build
node packages/mcp-server/dist/index.js --transport=http --port=8080

Then verify:

curl http://127.0.0.1:8080/health
curl -sS -D - http://127.0.0.1:8080/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"0.1"}}}'

Deployment

This repo deploys to Fly from packages/mcp-server/Dockerfile.

• Manual production deploy: fly deploy -c fly.toml
• Manual staging deploy: fly deploy -c fly.staging.toml
• Automatic staging deploy: push to staging
• Automatic production deploy: publish a GitHub release that targets main

Release Flow

Use the same promotion shape as the main Sanka app:

1. Open feature PRs into staging.
2. Merge staging after CI passes to deploy sanka-mcp-staging.
3. Validate the staging MCP endpoint.
4. Open staging -> main.
5. After main is ready, run Create new Sanka MCP Tag and Release.
6. The published release deploys production.

Required Fly apps and secrets:

• Production app: sanka-mcp
• Staging app: sanka-mcp-staging
• Set the same MCP_SERVER_* secrets on both apps unless staging intentionally uses a different auth stack.

Maintenance direction

This repository no longer depends on Stainless project access at runtime or for ongoing development. API coverage should be maintained directly in this repo.

The recommended next step is to adopt open-source OpenAPI tooling for updates to the internal client, rather than reintroducing a hosted generator dependency. See openapi-maintenance.md.

The repo now includes a starter typegen command:

pnpm generate:openapi-types

By default it reads the sibling Sanka spec at ../sanka-sdks/openapi.json.