TraQ

Provides MCP access to traQ data sources for messages, channels, and user information.

other

2

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mazrean-mcp-traq": {
      "command": "mcp-traQ",
      "args": [
        "bot"
      ],
      "env": {
        "MCP_TRAQ_BASE_URL": "<Base URL>",
        "MCP_TRAQ_BOT_TOKEN": "<Bot Token>"
      }
    }
  }
}

The MCP traQ Server lets you query traQ data sources through the MCP protocol, enabling you to retrieve messages, channels, user details, stamps, and pinned messages for use in your applications and bots.

How to use

Set up an MCP client to communicate with the traQ MCP server. You will run a local or remote MCP client that requests data such as message content, sender, timestamps, stamps, channel lists, and user information. The server exposes a stable interface for searching messages, locating channels, fetching user profiles, and retrieving stamps and pinned messages. Use your MCP client to initiate requests and consume the returned data in your workflows, dashboards, or automation tasks.

How to install

Prerequisites: none beyond having a compatible operating system to run the binary.

Download the appropriate binary for your OS and CPU from the releases page.
Give the binary execute permissions.
Place the binary in a directory that is in your PATH.
Prepare the MCP configuration by creating or updating your client’s configuration file with the MCP server entry shown below.

{
  "mcpServers": {
    "slack": {
      "command": "mcp-traQ",
      "args": ["bot"],
      "env": {
        "MCP_TRAQ_BOT_TOKEN": "<BotのAccess Token>",
        "MCP_TRAQ_BASE_URL": "<traQのベースURL(traPのサーバーの場合は不要)>"
      }
    }
  }
}

Additional sections

Environment variables shown in the sample config are required to authorize and direct the MCP server to the traQ instance. If you are using a traQ server separate from traP, specify the base URL in MCP_TRAQ_BASE_URL. The token MCP_TRAQ_BOT_TOKEN must be kept secure and not shared publicly.

Available tools

searchMessages

Query messages with content, sender, timestamp, and stamps similar to traQ search capabilities.

searchChannels

Retrieve channel information and lists available in traQ.

getUserInfo

Fetch user profile details for given user identifiers.

getStamps

List and inspect available stamps used in messages.

getPinnedMessages

Access messages that have been pinned in channels.