OAuth or a supported bearer-key connection
Your account · chosen workspaceAI access, built around control
Ticket tools for AI assistants.
Connect an approved AI assistant to your workspace’s tickets. Search and read issues, prepare drafts and make authorized changes through the same permission checks as Suparko itself.
THE CONNECTION PATH
- Active membership
- Granted ticket scopes
- Project and team access
Search, read, create, update or comment
Allowed tools · valid fieldsDRAFTReview a proposal
Validated change. Ticket stays unchanged.
DIRECTCommit an authorized change
Confirm the result in the actual ticket.
The access path
How an AI client reaches your tickets.
No direct database access. The adapter uses the same business validations and permissions as the workspace interface.
- 01Approved AI assistantYour client sends a focused tool call.
- 02Private MCP adapterChecks the credential, scopes and workspace.
- 03Authenticated Suparko APIApplies membership and project/team access.
- 04Application servicesValidates fields, revisions and writes.
Controls
Scoped by design.
A key for each identity
Create a separate credential for each workspace connection. Each key is bound to its workspace and can be revoked independently.
Only the ticket scopes you grant
Grant ticket reads, or ticket reads and writes. Each request checks current workspace, project and team permissions.
Draft or execute with control
Prepare a ticket change as a draft or execute an authorized write. Revision checks protect against stale updates.
Trace the source of an action
Connections and revocations carry workspace and initiating-user attribution in durable audit storage.
Ready to connect?
One endpoint. The right authentication.
Use the same public MCP server URL for each connection. OAuth selects the workspace during authorization; a workspace key is bound to its own workspace. Test a read and review a DRAFT proposal before requesting a committed change.
https://app.suparko.com/mcpNatural language, structured actions
“Show open issues in the launch project.”
list_issues · issues:read“Find the task about onboarding.”
search_issues · issues:read“Create a ticket for the release checklist.”
create_issue · issues:create“Update this ticket’s priority and add a comment.”
update_issue / add_issue_comment · issues:update / issues:comment
FAQ
Ticket MCP questions
Short, factual answers about how this part of Suparko works today. For more, read the full questions and answers.
Is live MCP access available now?
Yes. The remote endpoint supports permission-checked ticket reads and writes. ChatGPT uses OAuth and workspace selection; API-key clients use independently revocable workspace credentials.
Will every workspace have a different API key?
Yes. Each integration identity is bound to one workspace. Stored keys are hashed and independently revocable. Create a replacement key and revoke the old one when you need to change a client’s credential.
Can the connected AI read chats or Drive files?
No. Suparko’s current MCP tools are limited to tickets and their authorized context. Chat messages, Drive files, billing and user administration are outside the tool scope.
What is needed before connecting an AI client?
An active Suparko account and workspace membership. Add https://app.suparko.com/mcp in a compatible ChatGPT custom connection with OAuth, sign in and select your workspace. Workspace administrators can create keys for API-key clients in Private API & MCP settings. Client availability depends on your ChatGPT plan and workspace settings.
Next step
Plan the AI access your team needs.
Tell us how your projects run today. We’ll walk through the workspace with your workflow in mind.