relation-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RELATION_SUBDOMAIN | Yes | The subdomain of your Re:lation instance (the part before .relationapp.jp) | |
| RELATION_ACCESS_TOKEN | Yes | API access token generated from Re:lation admin UI | |
| RELATION_MESSAGE_BOX_ID | Yes | Default 受信箱 ID (message box ID) used as default for operations |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ticketsC | Search tickets by status, label, assignee, date range, and free-text query. Returns a paginated list. |
| get_ticketA | Fetch a single ticket by ticket_id, including all messages and metadata. |
| update_ticketB | Update ticket status, assignee, labels, color, or pending reason. Only provided fields are changed. |
| reply_mailA | Send an email reply on a Re:lation ticket. The email goes directly to the customer. Safety: you MUST pass Flow:
After a successful send the returned object contains the new message_id and ticket_id. |
| list_mail_accountsA | List the mail accounts (送信元) configured for a message_box. Use this to discover mail_account_id before calling reply_mail. |
| create_recordA | Create an internal "応対メモ" on a ticket. Visible only to the support team; the end customer never sees it. Use this for triage notes, investigation context, or handoff messages. |
| create_commentA | Post a team comment to a ticket. Not visible to the customer — used for internal discussion. |
| search_customersB | Search customers in the address book by email, phone, name, or company. |
| get_customerB | Fetch a single customer (address-book entry) by id. |
| list_labelsB | List all labels configured for a message_box. Useful before calling update_ticket with label_ids. |
| list_usersC | List operator users who can be assigned to tickets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Tool purposes are mostly distinct, but `create_comment` and `create_record` both create internal notes with nearly identical functionality, which could cause confusion for an agent. The descriptions help differentiate slightly.
All tool names follow a consistent `verb_noun` pattern in snake_case (e.g., `create_record`, `search_tickets`), making the naming predictable and unambiguous.
With 11 tools, the set is well-scoped for a ticket management system, covering the essential operations without being overly numerous or sparse.
Notable gaps exist: there is no `create_ticket` tool, so agents cannot initiate new tickets. Additionally, no delete or update operations for comments or records, and no customer creation/update, which limits the agent's ability to fully manage the domain.