TehProf Support
kz.tehprof.supportv2.3.0Updated Oct 4, 2026
Helpdesk tickets from your AI: find, reply, take, hold, complete — within your own role. OAuth.
Overview
AI-generated overview
Lets an assistant work with helpdesk tickets — find, reply to, take, hold, and complete them — within the user's own role.
- What it does
- This remote MCP server connects an assistant to a helpdesk ticketing system. According to the registry description, it exposes ticket operations: finding tickets, replying to them, taking them, putting them on hold, and completing them. Actions are scoped to the user's own role, and access is via OAuth. No individual tools are listed in the manifest.
- When to use it
- Worth adding when an assistant should help triage, answer, or progress support tickets without the user switching to the helpdesk interface. It suits support and service teams whose ticketing system is this one.
- Requirements
- A remote streamable HTTP endpoint at the provider's support host; nothing to install locally. Authentication is OAuth, and the manifest declares no API keys, environment variables, or headers. Network access to the provider's endpoint is required.
Before you install
The server can change ticket state — replying, taking, holding, and completing tickets — so an assistant's actions affect real support queues and customers. Access is limited to the user's own role, but the OAuth grant should be reviewed before connecting. Ticket content is sent to the provider's service.
Installation
In SourceWeft
- Open TehProf Support in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"helpdesk": {
"type": "http",
"url": "https://support.tehprof.kz/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v2.3.0LatestOct 4, 2026

