TehProf Support README

TehProf Support MCP Server

AI-powered helpdesk management via Model Context Protocol. Connect any MCP-compatible assistant (Claude, ChatGPT, Cursor, Cline) to your support workspace — no custom integration code.

TehProf Support (support.tehprof.kz) is a multi-tenant SaaS helpdesk built for IT service companies. This server exposes 36 AI tools covering knowledge search, ticket lifecycle, analytics, automation, and Bitrix24 CRM proxy — gated by subscription tier.

Zero installation: use the hosted endpoint at https://support.tehprof.kz/mcp.

Quick Start
Tools by Tier
Supported AI Clients
Architecture
Server Discovery
Authentication
Self-Hosting
Security
FAQ
Contributing
License

Quick Start

Option 1 — hosted (recommended)

Add to your MCP client config — no install, no server to run:

config.json

{
  "mcpServers": {
    "tehprof-support": {
      "url": "https://support.tehprof.kz/mcp",
      "transport": "streamable-http"
    }
  }
}

For authenticated access (unlocks tier-specific tools):

config.json

{
  "mcpServers": {
    "tehprof-support": {
      "url": "https://support.tehprof.kz/mcp",
      "transport": "streamable-http",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}

Option 2 — sanity check via curl

Terminal

curl -sX POST https://support.tehprof.kz/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

You should receive an initialize response with server capabilities.

Tools by Tier

The server gates tools by your TehProf Support plan. Anonymous (no API key) works out of the box.

Free — anonymous, no API key

Tool	What it does
`knowledge_search`	Full-text search across the knowledge base
`knowledge_read`	Read a specific article
`knowledge_list`	List articles by category
`onboarding_guide`	Step-by-step setup walkthrough
`onboarding_features`	Feature matrix by plan
`demo_create_ticket`	Create a ticket in the sandbox
`demo_view_ticket`	Inspect a demo ticket
`demo_workflow`	Walk the full ticket lifecycle
`pricing_plans`	List all pricing plans
`pricing_calculate`	Personalized plan recommendation
`system_health`	Platform status probe
`system_info`	Server capabilities
`system_tenant_info`	Your tenant metadata
`settings_get`	Read tenant settings
`settings_update`	Update available settings
`settings_operators`	List operators in your team

Starter

Tool	What it does
`tickets_list`	Filtered ticket list
`tickets_get`	Ticket + messages + participants
`analytics_dashboard`	KPI dashboard overview
`channels_list`	Messaging channels
`channels_status`	Per-channel connection state

Pro

Tool	What it does
`tickets_create`	Create new tickets; can sync the customer company/contact by your own stable external IDs (idempotent) and dedupe by `external_ref`
`tickets_reply`	Post replies on behalf of an operator
`tickets_update`	Change status / priority
`analytics_sla`	SLA compliance report
`analytics_operators`	Per-operator performance
`automation_rules_list`	List automation rules
`automation_rules_create`	Create new rules
`automation_rules_toggle`	Enable / disable rules
`webhooks_list`	Outbound webhooks

Business

Tool	What it does
`bitrix_contacts`	Search CRM contacts
`bitrix_deals`	List CRM deals
`bitrix_tasks`	Filter Bitrix24 tasks
`bitrix_task_create`	Create Bitrix24 tasks linked to tickets
`bitrix_users`	Portal user directory
`channels_configure`	Configure WA / TG / Email channels

Supported AI Clients

Works with any client that speaks MCP over Streamable HTTP:

Claude Desktop — claude_desktop_config.json
Claude Code — .mcp.json or ~/.claude/settings.json
Cursor — MCP settings panel
Cline / Continue.dev — config.json
ChatGPT (Custom GPT) — see gpt-config.md
Custom agents — any @modelcontextprotocol/sdk consumer

Architecture

Code

┌──────────────────────┐     Streamable HTTP      ┌──────────────────────┐
│  AI Client           │  ──────────────────────▶ │  MCP Server (this)   │
│  (Claude, GPT, ...)  │  JSON-RPC 2.0 + SSE      │  Node 20 + TS strict │
└──────────────────────┘                          └──────────┬───────────┘
                                                             │ HTTP localhost
                                                             ▼
                                                   ┌──────────────────────┐
                                                   │  PHP backend         │
                                                   │  mcp-auth.php        │
                                                   │  mcp-internal.php    │
                                                   └──────────┬───────────┘
                                                              │
                                                              ▼
                                                   ┌──────────────────────┐
                                                   │  SQLite (WAL)        │
                                                   │  Bitrix24 REST       │
                                                   └──────────────────────┘

Why Streamable HTTP (MCP 2025-03-26) and not stdio / SSE? Works through corporate proxies, scales horizontally, no long-lived connections to manage — the canonical transport for remote MCP.

Server Discovery

MCP clients can auto-discover this server via the .well-known endpoint:

Code

GET https://support.tehprof.kz/.well-known/mcp.json

The response lists server capabilities, auth requirements, and tier descriptors.

Authentication

Log in at support.tehprof.kz.
Settings → API Keys → Create.
Use it as Authorization: Bearer <key> in the MCP client header config.
Revoke / rotate any time from the same panel.

Keys are hashed at rest, rate-limited, and validated against the tenant's plan on every call.

The same tenant API key may also be used by GPT/OpenAPI clients against https://support.tehprof.kz/api/openapi.json as Authorization: Bearer <key>. Direct REST integrations that call /api/admin.php use X-Api-Key: <key> instead.

Security

Transport: TLS 1.3, HSTS, no mixed content.
CORS: allowlist (support.tehprof.kz, claude.ai, chat.openai.com) — no wildcard.
Sessions: 1-hour inactivity TTL, evicted every 5 minutes.
Tenant isolation: authenticated MCP/OpenAPI calls resolve the tenant from the API key; mismatched tenant_id is rejected with 403.
Internal bridge: mcp-auth.php is not public; mcp-internal.php requires Bearer auth for tenant data and write actions require write scope.
Secrets: never sent client-side, stored in HashiCorp Vault server-side.
Audit log: every tool call is recorded against the tenant.

Report vulnerabilities to ilay25@gmail.com (please do not open public issues for security).

Self-Hosting

For tenants who need the MCP server running in their own network:

bash

git clone https://github.com/tehprof/support-mcp
cd support-mcp
npm install
npm run build
MCP_PORT=8101 MCP_HOST=127.0.0.1 node dist/index.js

Set SUPPORT_BACKEND_URL to point at your Support backend. See CLAUDE.md for full env reference.

FAQ

Does this work without a TehProf account? Yes — anonymous access unlocks 16 free tools (knowledge, onboarding, demo, pricing, system, settings).

Can I use it with ChatGPT? Yes. Use a Custom GPT — configuration is in gpt-config.md.

What if my plan doesn't include a tool? The tool is hidden from tools/list — AI agents never see it. Upgrade at support.tehprof.kz.

How do I list all tools my plan exposes? Call MCP tools/list — the server filters in real time based on your Authorization header.

Where is the source code? Right here — github.com/tehprof/support-mcp. MIT licensed.

Contributing

Pull requests welcome. For non-trivial changes, please open an issue first to discuss.

License

MIT — see LICENSE.