Skip to main content
Sinjapp Business exposes a hosted Model Context Protocol server from the docs site. Use this name when adding the server to AI tools:
Use this URL:
The /mcp path is generated by Mintlify. Do not create a page at /mcp; use this guide page for setup instructions.

What The MCP Server Provides

  • Search across the Sinjapp Business documentation.
  • Read full documentation pages through the docs filesystem tool.
  • Access selected read-only Tenant API endpoints exposed from the OpenAPI specification.
  • Use the custom skill.md instructions to keep product naming, scope guidance, and safety rules consistent.

Accuracy Contract For AI Tools

When an AI tool uses this MCP server, it should:
  • Use Sinjapp Business as the product name.
  • Search the docs before answering integration questions.
  • Read the exact page or OpenAPI section before giving endpoint details.
  • Say when a requested endpoint, field, scope, or workflow is not documented.
  • Keep tenant API keys server-side and avoid exposing them in browser-only or mobile code.
  • Treat message sending, sender-number registration, API key creation, and API key revocation as side-effectful actions.
It should not:
  • Invent SDK packages, dashboard paths, webhook events, rate limits, or response fields.
  • Call the product TGO Business unless quoting legacy content.
  • Use /mcp as a normal docs page. It is a generated MCP endpoint.

Claude

  1. Open Claude settings.
  2. Go to Connectors.
  3. Select Add custom connector.
  4. Use Sinjapp Business as the name.
  5. Use https://docs.sinjapp.org/mcp as the URL.

Claude Code

Check that the server is available:

Cursor

Add this to your Cursor MCP configuration:

VS Code

Add this to .vscode/mcp.json:

Kiro

Kiro can load MCP servers from a workspace config file:
Or from a user-level config file:
Add this configuration:
In an active Kiro session, use /mcp to view loaded MCP servers and tools.

API Tools

The MCP server exposes only read-only or lookup Tenant API operations by default: Message sending and credential creation are not exposed as MCP tools by default. Keep those operations in your backend integration where you control approvals, audit logs, and API key storage. Use these prompts after deployment to check answer quality: