Sanka

What is Sanka?

Sanka is a hosted Model Context Protocol server that exposes Sanka's public API tools and read-only CRM tools through a single remote Streamable HTTP MCP endpoint. It is built as a TypeScript workspace and deployed on Fly.io. Developers building AI agents or assistants that need to interact with the Sanka platform use this server as the MCP bridge.

How to use Sanka?

Remote clients connect to the production endpoint at https://mcp.sanka.com/mcp (or the legacy alias https://mcp.sanka.com/sse) and authenticate with either an Authorization: Bearer <token> header or an x-sanka-api-key: <token> header. For local development, run pnpm install, pnpm build, then start the server with node packages/mcp-server/dist/index.js --transport=http --port=8080. The health of any instance can be verified via GET /health.

Key features of Sanka

• Remote Streamable HTTP MCP endpoint for the Sanka platform
• Exposes both general SDK tools and read-only CRM tools
• Authenticates via Bearer token or x-sanka-api-key header
• Health check endpoint at GET /health
• Production and staging environments hosted on Fly.io
• CI/CD pipeline with automatic staging deploys on push to staging

Use cases of Sanka

• AI agents reading Sanka CRM records in a read-only fashion
• AI assistants that invoke Sanka platform SDK tools via MCP
• Developers prototyping MCP clients against a staging Sanka endpoint before production use

FAQ from Sanka

What authentication methods does Sanka support?

Clients authenticate with either an Authorization: Bearer <token> header or an x-sanka-api-key: <token> header. The server forwards those credentials to the Sanka public API.

What tools does Sanka expose?

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

Where is the Sanka MCP server deployed?

The production service runs on Fly.io as the sanka-mcp app. The staging environment runs as sanka-mcp-staging. Both use the same deployment pipeline from the packages/mcp-server/Dockerfile.

How do I run Sanka locally for development?

Install dependencies with pnpm install, build the project with pnpm build, then start the server with node packages/mcp-server/dist/index.js --transport=http --port=8080. Verify it works by curling the health endpoint and sending an MCP initialize request.

What is the recommended endpoint for MCP clients?

The primary endpoint is POST /mcp. Legacy clients that expect an SSE-style path can use POST /sse as a compatibility alias.