Skip to content

Switches to FastMCP and adds resource support #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 20 commits into
base: main
Choose a base branch
from

Conversation

saramaebee
Copy link

@saramaebee saramaebee commented Jun 1, 2025

Hi team, super excited to be working on this with you. I apologise for the major overhaul to the code here, I understand if you are hesitant to accept it off the bat.

While I researching MCPs to figure out how to best utilise it in my workflow, I found a few good reasons for switching to the FastMCP framework. The 1.0 version of FastMCP is found in the Python mcp SDK, but they've continued iterating on it and just launched 2.2.0.

It has a lot of helpful features around logging/error handling/resource handling that I think will help us design a really useful tool.

The brunt of this PR was doing work to replace some scripts i'd been using to download ticket information (and comments/artifacts) for the LLM to analyze.

Please let me know if you have any questions. I've only just begun implementing some early stuff, I hope to add much deeper tooling as well.

Testing instructions

  • Checkout this branch
  • Configure your model to run the local branch
  • does this customer submit a lot of tickets?

Things to try asking a model connected to it

  • Can you help me debug TKT-12345?
  • Did the customer provide any screenshots to help explain the issue? (especially cool if you're using a model like Claude that can analyze photos)

Example of it in use

image

@saramaebee saramaebee requested a review from a team as a code owner June 1, 2025 18:40
@shivam-gupta-devrev
Copy link
Contributor

shivam-gupta-devrev commented Jun 4, 2025

Thanks for preparing this patch @saramaebee!! The PR looks pretty huge, can you break this down into smaller chunks for better and faster review:

  1. Integrate FastMCP and reorganise the existing tools in FastMCP compliant way.
  2. Add new tools as per specific use cases.

Keeping the PR small will ensure better & quicker reviews. Thanks!!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why named it claude.md ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants