Ticket API MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Ticket API MCP Servercreate a new support ticket with priority high"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Ticket API MCP Server
An MCP server exposing the internal Ticket API to MCP clients, built with FastMCP's OpenAPI integration.
Architecture & Authentication
The upstream API uses a two-hop auth model (static API Key + per-user short-lived JWT). This server bridges it to MCP clients by minting long-lived Personal Access Tokens (PATs) and transparently handling upstream JWT refresh.
sequenceDiagram
participant Client as MCP Client
participant Server as Ticket MCP Server
participant DB as SQLite (Encrypted)
participant Upstream as Upstream Ticket API
Note over Client, Server: 1. One-time Setup
Client->>Server: POST /register (username, password)
Server->>Upstream: Validate credentials
Server->>DB: Store hashed PAT & encrypted password
Server-->>Client: Returns never-expiring PAT (tkt_...)
Note over Client, Server: 2. Ongoing Tool Calls
Client->>Server: Tool Call (Bearer PAT)
Server->>DB: Verify PAT hash
alt Cached JWT expired/missing
Server->>DB: Decrypt password
Server->>Upstream: Re-login to get fresh JWT
end
Server->>Upstream: Forward Tool Call + Bearer JWT
Upstream-->>Server: Tool response
Server-->>Client: Tool responseRelated MCP server: tickiti-mcp
Running Locally
pip install -e ".[dev]"
cp .env.example .env # Fill in keys
ticket-mcp-server
# MCP endpoint: http://localhost:8000/sse
# Register a PAT: POST http://localhost:8000/register {"username": "...", "password": "..."}
# Revoke a PAT: POST http://localhost:8000/revoke (Authorization: Bearer <PAT>)
# Health check: GET http://localhost:8000/health (unauthenticated)Connect with any MCP client using the standard SSE transport at http://localhost:8000/sse with Authorization: Bearer <your-tkt_-token>.
Running with Docker
docker build -t ticket-mcp-server .
docker run -p 8000:8000 \
-v ticket-mcp-data:/app/data \
-e TICKET_MCP_UPSTREAM_API_KEY=<your-service-key> \
-e TICKET_MCP_CREDENTIAL_ENCRYPTION_KEY=<your-fernet-key> \
ticket-mcp-server(Note: The -v volume mount is required to persist PATs across container restarts.)
Configuration
Set via environment variables (prefix TICKET_MCP_):
Variable | Required | Default | Description |
| yes | — | Service-level |
| yes | — | Fernet key for credentials |
| no |
| Upstream API base URL |
| no |
| SQLite PAT store |
| no |
| Bind host/port |
Generate an encryption key:
python -c "from cryptography.fernet import Fernet; print(Fernet.generate_key().decode())"Tests
pip install -e ".[dev]"
pytest -v(Tests use a mock upstream API to safely exercise the full PAT lifecycle.)
Copyright©️ Codebasics Inc. All rights reserved.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/codebasics/ticket-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server