MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
作者による説明(英語の原文)
Redmine for AI agents: issues, projects, wiki, attachments, time entries and release analytics
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
REDMINE_URL, REDMINE_API_KEY, REDMINE_MCP_WRITE_ENABLED「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"redmine": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"REDMINE_URL",
"-e",
"REDMINE_API_KEY",
"-e",
"REDMINE_MCP_WRITE_ENABLED",
"ghcr.io/igorolv/redmine-mcp-server:0.1.1"
],
"env": {
"REDMINE_URL": "your-value",
"REDMINE_API_KEY": "your-value",
"REDMINE_MCP_WRITE_ENABLED": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add redmine --env REDMINE_URL=your-value --env REDMINE_API_KEY=your-value --env REDMINE_MCP_WRITE_ENABLED=your-value -- docker run -i --rm -e REDMINE_URL -e REDMINE_API_KEY -e REDMINE_MCP_WRITE_ENABLED ghcr.io/igorolv/redmine-mcp-server:0.1.1動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"redmine": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"REDMINE_URL",
"-e",
"REDMINE_API_KEY",
"-e",
"REDMINE_MCP_WRITE_ENABLED",
"ghcr.io/igorolv/redmine-mcp-server:0.1.1"
],
"env": {
"REDMINE_URL": "your-value",
"REDMINE_API_KEY": "your-value",
"REDMINE_MCP_WRITE_ENABLED": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"redmine": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"REDMINE_URL",
"-e",
"REDMINE_API_KEY",
"-e",
"REDMINE_MCP_WRITE_ENABLED",
"ghcr.io/igorolv/redmine-mcp-server:0.1.1"
],
"env": {
"REDMINE_URL": "your-value",
"REDMINE_API_KEY": "your-value",
"REDMINE_MCP_WRITE_ENABLED": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
REDMINE_MCP_WRITE_ENABLED envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント igorolv で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:REDMINE_URL, REDMINE_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.1.1)がレジストリに届いたのは39 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにDockerも必要です。
同じカテゴリには:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
An MCP server retrieving transcripts of YouTube videos
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
A local MCP server for accessing a corporate Redmine instance. It exposes a limited set of write operations for issues, time entries, and wiki alongside the read tools; set REDMINE_MCP_WRITE_ENABLED=false to run fully read-only. It lets AI agents (Claude Code, Cursor, VS Code Copilot, etc.) work with issues, projects, members, versions, wiki, attachments, time entries, and reference data.
This documentation covers installing and connecting Redmine MCP Server itself. Installing and configuring the AI clients themselves is out of scope here.
redmine-mcp-server.jar from the latest release, or build it yourself: ./gradlew bootJar (see Build). A Docker image is published as well.REDMINE_URL and REDMINE_API_KEY (see Configuration).For Claude Code that is one command:
claude mcp add --scope user -e REDMINE_URL=https://redmine.example.com -e REDMINE_API_KEY=your_key -- redmine java -jar /path/to/redmine-mcp-server.jar
The server supports only the stdio transport.
┌─────────────┐ stdio ┌──────────────────┐ REST API ┌──────────┐
│ AI agent │ <------------> │ redmine-mcp- │ -------------> │ Redmine │ │ (Claude Code│ stdin/stdout │ server (Java) │ HTTP + API │ (corp.) │ │ Cursor...) │ │ │ Key │ │ └─────────────┘ └──────────────────┘ └──────────┘
The AI client launches the server as a child process; communication follows the MCP protocol over stdin/stdout.
The server exports 32 read-only MCP tools plus 7 write tools by default. Set REDMINE_MCP_WRITE_ENABLED=false to remove the write tools and run fully read-only.
| Tool | Description |
|---|---|
getCurrentUser | Current user: ID, login, groups, projects. Useful for "my issues" filtering |
| Tool | Description |
|---|---|
listProjects | List of all accessible projects |
getProject | Project details: trackers, modules, description |
listProjectMembers | Project members with roles |
listVersions | Project versions (milestones) |
| Tool | Description |
|---|---|
listIssues | Issue list with filters: project, status, tracker, assignee, priority, version, saved query, custom fields (customFieldFilters in cf_ =value format), sorting |
searchIssues | Full-text issue search with detailed results |
getIssue | Issue details: description, status, assignee, dates, notes, relations, custom fields, attachments, linked revisions (changesets). Parameters: issueId, focus (default, implementation, timeline, full; optional) |
getIssueJournal | A single complete issue journal note/event without response compression. Parameters: issueId, journalId |
getMyIssues | Issues of the current user. Parameters: projectId, statusId, sort, limit, offset |
getIssueTree | Parent chain and subtasks. root and ancestors keep the Issue JSON shape but contain compact context; call getIssue for full details or relations. Parameters: issueId, depth (default 2, max 5) |
getIssueHistory | Creation and every journal event, with status intervals. Long text is shortened; journalId identifies the full entry for getIssueJournal. Follow nextOffset with the optional offset parameter until it is absent. |
These tools appear in tools/list by default; set REDMINE_MCP_WRITE_ENABLED=false to remove them:
| Tool | Description |
|---|---|
createIssue | Creates an issue. Supports core Redmine fields and custom fields via customFieldsJson |
updateIssue | Partially updates the specified fields of an existing issue |
addIssueNote | Adds a note to the issue journal |
attachFileToIssue | Uploads a file from any readable local path and attaches it to the issue |
createTimeEntry | Creates a time entry for the user from REDMINE_API_KEY; accepts exactly one of issueId/projectId, hours, date, activity, comment, and custom fields |
createWikiPage | Creates a wiki page and rejects the request if the page already exists |
updateWikiPage | Fully replaces the wiki page text, requiring the optimistic-lock version returned by getWikiPage |
Redmine itself enforces the permissions, workflow, and required-field rules of the REDMINE_API_KEY user. The MCP server introduces no additional model of "own" issues or notes. To make AI-created issues recognizable, the description of an issue created by createIssue is prefixed with AI_EDIT: by default (updateIssue does not add it). Notes, time-entry comments, wiki revision comments, and uploaded file names are not marked by default; each marker is configured separately with a REDMINE_MCP_WRITE_*_PREFIX variable (see Configuration), and an empty value turns it off. Issue descriptions and notes get the prefix on its own line followed by a blank line; single-line fields (time-entry and wiki revision comments) get the prefix and a space; file names get the prefix with no separator. Wiki page markup itself is never changed.
Editing and deleting existing notes is not implemented: the targeted Redmine 4.0.4 does not provide a compatible REST API for it. Editing and deleting time entries; deleting, renaming, and protecting wiki pages; and creating time entries on behalf of another user are outside the current operation set.
| Tool | Description |
|---|---|
searchAll | Global Redmine search: issues, wiki, news, documents, commits, etc. Parameters: searchQuery, projectId, types, limit, offset |
| Tool | Description |
|---|---|
getAttachment | Downloads the original attachment file into a local snapshot directory, returns localPath/fileUri, and immediately adds text context to parts[] if the format is supported: txt/log/xml/json/csv, PDF, Word (.docx), Excel (.xlsx), PowerPoint (.pptx), ZIP. A ZIP may yield a separate part per entry. A .docx yields one text part: pandoc markdown when pandoc is available, POI plain text otherwise. Parameters: issueId, attachmentId, maxChars, partLimit (see *Processing Limits*) |
getWikiPage | Content of a project wiki page |
listWikiPages | List of all wiki pages of a project |
searchWikiPages | Full-text search across wiki pages. Parameters: searchQuery, projectId, limit, offset |
| Tool | Description |
|---|---|
listTimeEntries | Logged time with filters: project, issue, user, period |
getMyTimeEntries | Logged time of the current user. Parameters: projectId, issueId, from, to, limit, offset |
| Tool | Description |
|---|---|
listQueries | Saved queries (custom filters) — ID + name. Use the ID with listIssues(queryId) to apply the filter, including custom-field filters |
listStatuses | All issue statuses (ID + name) — for filtering in listIssues |
listTrackers | All trackers (ID + name) — for filtering in listIssues |
listPriorities | All priorities (ID + name) — for filtering in listIssues |
listIssueCategories | Issue categories of a project (ID + name) |
listTimeEntryActivities | Activity types for interpreting existing time entries (ID + name) |
| Tool | Description |
|---|---|
getProjectSummary | Aggregated project summary: overall open/closed count; analyzed open issues broken down by status, tracker, priority, assignee; overdue issues; estimated/spent hours. Analyzes up to 500 open issues and returns a truncation flag. Parameters: projectId, versionId (optional) |
getUserWorkload | Workload analysis: open issues by project and priority, overdue issues, top issues. Analyzes up to 500 open issues and returns a truncation flag. Parameters: userId (optional, defaults to current user), projectId (optional) |
getVersionChangelog | Version issues grouped by tracker, open/closed statistics. Analyzes up to 500 issues and returns a truncation flag. Parameters: projectId, versionId |
getBlockerChain | Recursive traversal of the blocking chain (blocks/blocked_by) upward and downward, limited to depth 10 and 30 loaded issues. Parameters: issueId |
getStaleIssues | Open issues not updated for N days, oldest first. Parameters: projectId, daysSinceUpdate (default 30), limit |
getReleaseRisks | Release risk assessment: blockers, overdue items, high-priority issues, unassigned issues. Analyzes up to 500 open issues and returns a truncation flag. Parameters: projectId, versionId |
compareVersions | Compares two versions: unique issues, shared issues, closure percentage. Analyzes up to 500 issues per version and returns a truncation flag. Parameters: projectId, versionId1, versionId2 |
With REDMINE_MCP_WRITE_ENABLED=false all tools are read-only and no data in Redmine is modified.
Tools are grouped by domain, and each group can be disabled via an environment variable. All groups are enabled by default — the out-of-the-box tool manifest is unchanged. Disabling groups shrinks the MCP tools/list manifest that the client loads into model context at session start. This helps small-context (local) models: disable unneeded groups so only the tools the model actually needs remain.
| Variable | Group (tools) |
|---|---|
REDMINE_MCP_TOOLS_ISSUE | Issues (core): listIssues, searchIssues, getIssue, getMyIssues, getIssueJournal |
REDMINE_MCP_TOOLS_ISSUE_STRUCTURE | Issue structure/history: getIssueTree, getIssueHistory |
REDMINE_MCP_TOOLS_PROJECT | Projects: listProjects, getProject, listProjectMembers, listVersions |
REDMINE_MCP_TOOLS_SEARCH | Search: searchAll |
REDMINE_MCP_TOOLS_ATTACHMENT | Attachments: getAttachment |
REDMINE_MCP_TOOLS_WIKI | Wiki: getWikiPage, listWikiPages, searchWikiPages |
REDMINE_MCP_TOOLS_TIME_ENTRY | Time entries: listTimeEntries, getMyTimeEntries |
REDMINE_MCP_TOOLS_REFERENCE_DATA | Reference data: listQueries, listStatuses, listTrackers, listPriorities, listIssueCategories, listTimeEntryActivities |
REDMINE_MCP_TOOLS_USER | User: getCurrentUser |
REDMINE_MCP_TOOLS_ISSUE_ANALYTICS | Issue analytics: getBlockerChain, getStaleIssues |
REDMINE_MCP_TOOLS_RELEASE_ANALYTICS | Release/project analytics: getProjectSummary, getUserWorkload, getVersionChangelog, getReleaseRisks, compareVersions |
Each variable accepts true (default) or false. Example: to keep only issue and project work, disable the remaining groups — REDMINE_MCP_TOOLS_RELEASE_ANALYTICS=false, `REDMI
冒頭だけを表示しています。続きはリポジトリで読めます