TISYM MCP Server — Documentation

TISYM provides an MCP (Model Context Protocol) server that gives AI assistants access to helpdesk, project management, invoicing and work report data. This page describes the available tools, permissions and how to connect.

MCP URL: https://mcp.tisym.com
Protocol: MCP 2025-03-26, JSON-RPC 2.0, Streamable HTTP
Authentication: OAuth 2.0 Authorization Code Flow + PKCE

User Roles & Permissions

Admin

Full access to all 26 tools — tickets, projects, customers, users, invoices and work reports.

Solver

Helpdesk + projects + work reports. Invoicing and user management not available.

Contact (customer)

View and create own tickets and projects. Read-only — no access to other users' data.

Available Tools

Tool	Description	Admin	Solver	Contact
System
`get_instance_info`	Instance information	✅	✅	✅
Tickets
`list_tickets`	List tickets with filters	✅	✅	✅
`get_ticket_details`	Ticket detail with history	✅	✅	✅
`create_ticket`	Create a new ticket	✅	✅	✅
`add_ticket_note`	Add a note to a ticket	✅	✅	✅
`delegate_ticket`	Delegate ticket to a solver	✅	✅	❌
`get_attachment`	Download ticket attachment	✅	✅	✅
Projects
`list_projects`	List projects	✅	✅	✅
`get_project_details`	Project detail with members	✅	✅	✅
`create_project`	Create a project	✅	❌	❌
`update_project`	Update a project	✅	❌	❌
`delete_project`	Delete a project	✅	❌	❌
Customers
`list_customers`	List customers	✅	❌	❌
`get_customer_details`	Customer detail	✅	❌	❌
`create_customer`	Create a customer	✅	❌	❌
`update_customer`	Update a customer	✅	❌	❌
`delete_customer`	Delete a customer	✅	❌	❌
Work Reports
`list_work_reports`	List work reports	✅	✅	❌
`create_work_report`	Log a work report	✅	✅	❌
`export_work_reports_csv`	Export work reports to CSV	✅	✅	❌
Invoices
`list_invoices`	List invoices with filters	✅	❌	❌
`get_invoice_details`	Invoice detail	✅	❌	❌
`create_invoice`	Create an invoice	✅	❌	❌
`update_invoice`	Update an invoice	✅	❌	❌
`mark_invoice_paid`	Mark invoice as paid	✅	❌	❌
`delete_invoice`	Delete an invoice	✅	❌	❌

Usage Examples

All examples below are based on real data from the TISYM test instance (test.tisym.com) and can be repeated at any time — they only read data, nothing is modified.

Example 1 — TISYM instance info and current user
Prompt: "Which TISYM instance is this and who am I logged in as?"
AI calls: get_instance_info + get_current_user
Sample response:

You are logged in as Test (admin) into instance "Test" (test.tisym.com).
Available languages: Czech (cs), English (en).
Your language: English, timezone: Europe/Berlin.

Example 2 — Unsolved and postponed tickets sorted by priority
Prompt: "Show me tickets that are still unsolved or postponed — sorted by priority."
AI calls: list_tickets with id_states: [1, 7], sortBy: priority, sortDir: asc
Sample response:

#16348 — PCI-DSS compliance review [Critical] — Postponed — Payment Gateway Integration
#16347 — Payment gateway integration - Stripe & PayPal [High] — Unsolved — E-Commerce Platform Development
#16344 — Server migration - phase 1 planning [Standard] — Postponed — Cloud Infrastructure Upgrade
#16350 — Analytics dashboard for supply chain KPIs [Low] — Unsolved — Supply Chain Tracking System

Example 3 — Which projects am I working on?
Prompt: "List the active projects."
AI calls: list_projects with active: true
Sample response:

Active projects (4):
• Cloud Infrastructure Upgrade — customer: TechVision Solutions Ltd.
• E-Commerce Platform Development — customer: Greenfield Digital Inc.
• Payment Gateway Integration — customer: Blue Harbour Fintech Pty Ltd
• Supply Chain Tracking System — customers: Ironbridge Consulting Ltd., Northern Route Logistics Ltd.

Example 4 — Ticket detail with full history
Prompt: "What is the status of ticket #16347 and what has been done on it?"
AI calls: get_ticket_details with id: 16347
Sample response:

Ticket: Payment gateway integration - Stripe & PayPal
Project: E-Commerce Platform Development | Status: Unsolved | Priority: High

Notes (2):
1. Stripe integration completed and tested in sandbox. PayPal OAuth flow implemented.
   Webhook endpoints deployed to staging. Refund flow needs further testing.
   (5 hours logged)
2. [INTERNAL] Stripe sandbox credentials need rotating before production go-live.
   Do not share current test keys with client.

Example 5 — Work reports for a project
Prompt: "How many hours have been logged on the Cloud Infrastructure Upgrade project?"
AI calls: list_work_reports with idProject: 601
Sample response:

Work reports — Cloud Infrastructure Upgrade:

CI/CD pipeline setup (ticket #16345):
  Pipeline fully configured and tested. All stages passing including integration tests.
  Production release requires manual approval from Sophie Caldwell.
  Time: 3.5 h | Author: Test

Total: 3.5 h (1 report)

Questions about integration: info@tisym.com