MCP Connector

Tony Simek

Dronelink team - Thank you.  The MCP connector is nothing short of AMAZING.  Mission planning was already a breeze in Dronelink, but now thanks to the tie-in, my mission planning time just dropped to trivial/fun levels.  I just cannot believe how amazing this is working.  Other than personal touch-ups, I may never manually plan a mission start to finish again.  I am adding skills on my side to handle so much heavy lifting I cannot even think straight.  

Bottom line - THANK YOU Dronelink.  As usual, you have added amazing value to this service.  

 

0

Comments

12 comments

  • Comment author
    Barry Houldsworth Dronelink Expert Dronelink Expert

    Agreed.

    I assume you saw the video on that?  https://youtu.be/J5OB4dtNnPo

    1
  • Comment author
    Tony Simek

    Yes!  But did not watch it yet.  I saw it, and knew immediately that it was going to consume my life.  : )  It is on my to-watch list!!!  Thankfully, I have connections to the token factory.  : )

     

    0
  • Comment author
    Tony Simek

    Barry Houldsworth Best practice, create a repository just for the mcp created inbound plans.  : )

    0
  • Comment author
    Robert

    The ability to automate most of the planning while keeping personal adjustments in your hands makes the MCP connector especially exciting.

    0
  • Comment author
    Barry Houldsworth Dronelink Expert Dronelink Expert

    I need those connections!  Actually...it's probably good that I don't 😊

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Glad you're liking it! Anything else you want to see added to the feature?

    1
  • Comment author
    Tony Simek

    Yes! Mcp support to let me set mission components to use ground level agl instead of takeoff. Then the only thing I have to do manually is set my specific required takeoff area.

    0
  • Comment author
    Tony Simek

    Also if mcp allowed mission history access! That would be amazing

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Thanks Tony, both are good ideas. Ground-level altitude is on our list. Do you use the default terrain data or your own imported DEM?

    For mission history, what would you ask Claude to do with it? For example: summarize flights by date or site, compare what was flown with the plan, find missions that had problems, or pull photo counts and flight times. That tells us which data to expose first.

    0
  • Comment author
    Tony Simek

    Default terrain - that’s why I love offsets visible in ui on day of flight to account for the unexpected.

    History because then I can compare ro previous flown missions. Also generate pdfs of the mission and with dates and times extract details about shooting conditions from other sources - weather, angle of sun etc. i’m gonna send you an email directly of an example that I produce now when I create a mission using the MCP

    0
  • Comment author
    Barry Houldsworth Dronelink Expert Dronelink Expert

    Tony Simek

    If you have not used the DEM import...that is covered in the video going out tomorrow :)

    0
  • Comment author
    Tony Simek

    That’s funny. I look forward to it, of course, because you always do great video. I’m familiar with DEM, but I do not do that out of need for speed

    0

Please sign in to leave a comment.