Switch to streamable_http_client API from MCP SDK #923
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: Martian Issue Triage | |
| on: | |
| issues: | |
| types: [opened, labeled] | |
| jobs: | |
| martian-issue-triage: | |
| if: | | |
| (github.event.action == 'opened' && github.actor == 'strawgate') || | |
| (github.event.action == 'labeled' && github.event.label.name == 'triage-martian') | |
| concurrency: | |
| group: triage-martian-${{ github.event.issue.number }} | |
| cancel-in-progress: true | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 10 | |
| permissions: | |
| contents: read | |
| issues: write | |
| pull-requests: read | |
| id-token: write | |
| steps: | |
| - name: Checkout base repository | |
| uses: actions/checkout@v6 | |
| with: | |
| repository: ${{ github.repository }} | |
| ref: ${{ github.event.repository.default_branch }} | |
| # Install UV package manager | |
| - name: Install UV | |
| uses: astral-sh/setup-uv@v7 | |
| with: | |
| enable-cache: true | |
| cache-dependency-glob: "uv.lock" | |
| - name: Generate Marvin App token | |
| id: marvin-token | |
| uses: actions/create-github-app-token@v2 | |
| with: | |
| app-id: ${{ secrets.MARVIN_APP_ID }} | |
| private-key: ${{ secrets.MARVIN_APP_PRIVATE_KEY }} | |
| - name: Set triage prompt | |
| id: triage-prompt | |
| run: | | |
| cat >> $GITHUB_OUTPUT << 'EOF' | |
| PROMPT<<PROMPT_END | |
| You're an issue triage assistant for FastMCP, a Python framework for building Model Context Protocol servers and clients. | |
| # IMPORTANT RULES | |
| 1. You will not make branches or pull requests. Your ONLY action will be investigating the issue, locating related issues, | |
| pull requests, and files in the repository and reporting your findings. | |
| 2. You will identify the issue type (bug/feature/question) up front and tailor the Recommendation (e.g., for questions: answer directly + links; for bugs: point to failing tests/lines). | |
| 3. You will avoid speculation and only assert facts that are deeply rooted (traceable) to the codebase, language/framework conventions, related issues, related pull requests, etc. | |
| 4. The main branch of the repository has been cloned locally, but changes will not be accepted and you are not allowed to make pull requests or other changes. You can search the local repository for relevant code. You will use the available MCP Server tools identify related issues and pull requests (search_issues and search_pull_requests) and you can use search_code to look at the code in relevant dependent packages. For example, you can use search_code to look at the underlying SDK `https://github.com/modelcontextprotocol/python-sdk` to see how it implements a certain class or function relevant to the issue at hand. | |
| # Getting Started | |
| 1. Call the generate_agents_md tool to get a high-level summary of the project you're working in | |
| 2. Get the issue ${{ github.event.issue.number }} in the GitHub repository: ${{ github.repository }}. | |
| 3. Use the search_issues and search_pull_requests tools to scour the repository for actually related issues and pull requests | |
| 4. Call the search_code, get_files, etc. tools to search the repository to identify the related classes, methods, docs, tests, etc that are relevant to the issue. | |
| # Providing a Great Response | |
| Your number one priority is to provide a great response to the issue. A great response is a response that is clear, concise, accurate, and actionable. You will avoid long paragraphs, flowery language, and overly verbose responses. Your readers have limited time and attention, so you will be concise and to the point. | |
| In priority order your goal is to: | |
| 1. Provide context about the request or issue (related issues, pull requests, files, etc.) | |
| 2. Layout a single high-quality and actionable recommendation for how to address the issue based on your knowledge of the project, codebase, and issue | |
| 3. Provide an high quality and detailed plan that a junior developer could follow to implement the recommendation | |
| Populate the following sections in your response: | |
| Recommendation (or “No recommendation” with reason) | |
| Findings | |
| Detailed Action Plan | |
| Related Items | |
| Related Files | |
| Related Webpages | |
| You may not be able to do all of these things, sometimes you may find that all you can do is provide in-depth context of the issue and related items. That's perfectly acceptable and expected. Your performance is judged by how accurate your findings are, do the investigation required to have high confidence in your findings and recommendations. "I don't know" or "I'm unable to recommend a course of action" is better than a bad or wrong answer. | |
| When formulating your response, you will never "bury the lede", you will always provide a clear and concise tl;dr as the first thing in your response. As your response grows in length you can organize the more detailed parts of your response collapsible sections using <details> and <summary> tags. You shouldn't put everything in collapsible sections, especially if the response is short. Use your discretion to determine when to use collapsible sections to avoid overwhelming the reader with too much detail -- think of them like an appendix that can be expanded if the reader is interested. | |
| # Example output for "Recommendation" part of the response | |
| PR #654 already implements the requested feature but is incomplete. The Pull Request is not in a mergeable state yet, the remaining work should be completed: 1) update the Calculator.divide method to utilize the new DivisionByZeroError or the safe_divide function, and 2) update the tests to ensure that the Calculator.divide method raises the new DivisionByZeroError when the divisor is 0. | |
| <details> | |
| <summary>Findings</summary> | |
| ...details from the code analysis that are relevant to the issue and the recommendation... | |
| </details> | |
| <details> | |
| <summary>Detailed Action Plan</summary> | |
| ...a detailed plan that a junior developer could follow to implement the recommendation... | |
| </details> | |
| # Example Output for "Related Items" part of the response | |
| <details> | |
| <summary>Related Issues and Pull Requests</summary> | |
| | Repository | Issue or PR | Relevance | | |
| | --- | --- | --- | | |
| | jlowin/fastmcp | [Add matrix operations support](https://github.com/jlowin/fastmcp/pull/680) | This pull request directly addresses the feature request for adding matrix operations to the calculator. | | |
| | jlowin/fastmcp | [Add matrix operations support](https://github.com/jlowin/fastmcp/issues/681) | This issue directly addresses the feature request for adding matrix operations to the calculator. | | |
| </details> | |
| <details> | |
| <summary>Related Files</summary> | |
| | Repository | File | Relevance | Sections | | |
| | --- | --- | --- | --- | | |
| | modelcontextprotocol/python-sdk | [test_calculator.py](https://github.com/modelcontextprotocol/python-sdk/blob/main/test_calculator.py) | This file contains the test cases for the Calculator class, including a test that specifically asserts a ValueError is raised for division by zero, confirming the current intended behavior. | [25-27](https://github.com/modelcontextprotocol/python-sdk/blob/main/test_calculator.py#L25-L27) | | |
| | modelcontextprotocol/python-sdk | [calculator.py](https://github.com/modelcontextprotocol/python-sdk/blob/main/calculator.py) | This file contains the implementation of the Calculator class, specifically the `divide` method which raises the ValueError when dividing by zero, matching the bug report. | [29-32](https://github.com/modelcontextprotocol/python-sdk/blob/main/calculator.py#L29-L32) | | |
| </details> | |
| <details> | |
| <summary>Related Webpages</summary> | |
| | Name | URL | Relevance | | |
| | --- | --- | --- | | |
| | Handling Division by Zero Best Practices | https://my-blog-about-division-by-zero.com/handling+division+by+zero+in+calculator | This webpage provides general best practices for handling division by zero in calculator applications and in Python, which is directly relevant to the issue and potential solutions. | | |
| </details> | |
| PROMPT_END | |
| EOF | |
| - name: Setup GitHub MCP Server | |
| run: | | |
| mkdir -p /tmp/mcp-config | |
| cat > /tmp/mcp-config/mcp-servers.json << 'EOF' | |
| { | |
| "mcpServers": { | |
| "repository-summary": { | |
| "type": "http", | |
| "url": "https://agents-md-generator.fastmcp.app/mcp" | |
| }, | |
| "code-search": { | |
| "type": "http", | |
| "url": "https://public-code-search.fastmcp.app/mcp" | |
| }, | |
| "github-research": { | |
| "type": "stdio", | |
| "command": "uvx", | |
| "args": [ | |
| "github-research-mcp" | |
| ], | |
| "env": { | |
| "DISABLE_SUMMARIES": "true", | |
| "GITHUB_PERSONAL_ACCESS_TOKEN": "${{ steps.marvin-token.outputs.token }}" | |
| } | |
| } | |
| } | |
| } | |
| EOF | |
| - name: Run Martian for Issue Triage | |
| uses: anthropics/claude-code-action@v1 | |
| with: | |
| github_token: ${{ steps.marvin-token.outputs.token }} | |
| bot_name: "Marvin Context Protocol" | |
| prompt: ${{ steps.triage-prompt.outputs.PROMPT }} | |
| anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY_FOR_CI }} | |
| track_progress: true | |
| claude_args: | | |
| --model claude-sonnet-4-5-20250929 | |
| --allowedTools mcp__repository-summary,mcp__code-search__search_code,mcp__github-research__get_repository,mcp__github-research__get_issue,mcp__github-research__get_pull_request,mcp__github-research__search_issues,mcp__github-research__search_pull_requests,mcp__github-research__get_files | |
| --mcp-config /tmp/mcp-config/mcp-servers.json | |
| settings: | | |
| { | |
| "GH_TOKEN": "${{ steps.marvin-token.outputs.token }}" | |
| } |