MCP question

Status: Open · Asked by DuPont Octavius on · 0 views

unbleachedmuslin — Question ·

Can a support person take a look at my MCP build. I built it on pabbly but my agent is returning a 500 Internal Server Error. This suggests the issue is still persisting on the API server side. Hoping support can provide some insight on this.

I've built 20 total tools and none work.

Preeti Paryani — Reply ·

Hi @unbleachedmuslin,

Thanks for sharing the details.

We’ve reviewed your workflow, and this appears to be more likely related to API configuration rather than an issue with Pabbly Connect itself.

To assist you further, could you please share:

  • The API documentation
  • The specific endpoint you are trying to execute

Once we have these details, we’ll review the setup and help you troubleshoot the issue more effectively.

Looking forward to your response.

unbleachedmuslin — Reply ·
Hi @unbleachedmuslin,

Thanks for sharing the details.

We’ve reviewed your workflow, and this appears to be more likely related to API configuration rather than an issue with Pabbly Connect itself.

To assist you further, could you please share:

  • The API documentation
  • The specific endpoint you are trying to execute

Once we have these details, we’ll review the setup and help you troubleshoot the issue more effectively.

Looking forward to your response.


Thank you for your response. This is my first time attempting to build an MCP so I apologize in advance should I not express the terms correctly.
The API documentation is found here https://api.agencyhandy.com/api/v1/docs/ As for endpoints (if I understand this correctly) I have 20 different endpoints as a result of 20 different tools. I created a folder called Agency Handy MCP that has all of the workflows within them.
Preeti Paryani — Reply ·

Hi @unbleachedmuslin,

Thank you for the update and for sharing the details.

We have checked the API docs and tried to determine whether there is any connection or authentication-related issue, but the error still persists. Here's what we suggest you check:

  1. API Token Validation
    • Please confirm that the API token you are using is the latest one.
    • Ensure that it has all the required permissions/scopes for the endpoints you are trying to access.
    • If the token has expired or was regenerated, kindly update it in your workflows.
  2. Test via API Documentation
    • Try executing the same endpoint directly from the API docs using the “Try it out” option:
      https://api.agencyhandy.com/api/v1/docs/
    • If the API fails there as well, the issue is confirmed to be on the API side rather than Pabbly Connect.
  3. Endpoint Verification
    • Double-check headers, authentication method, and request body format used in your MCP tools.

If you continue to face issues, we can assist you over a live call to review the setup end-to-end.

Please book a slot using the link below:
https://calendly.com/d/ctw5-2bb-rct

Looking forward to your response.

unbleachedmuslin — Reply ·

I have reason to believe the transport method is also an issue. I change the method to https but it doesn't save. With each refresh it still appears as SSE. Please advise.

unbleachedmuslin — Reply ·
Hi @unbleachedmuslin,

Thank you for the update and for sharing the details.

We have checked the API docs and tried to determine whether there is any connection or authentication-related issue, but the error still persists. Here's what we suggest you check:

  1. API Token Validation
    • Please confirm that the API token you are using is the latest one.
    • Ensure that it has all the required permissions/scopes for the endpoints you are trying to access.
    • If the token has expired or was regenerated, kindly update it in your workflows.
  2. Test via API Documentation
    • Try executing the same endpoint directly from the API docs using the “Try it out” option:
      https://api.agencyhandy.com/api/v1/docs/
    • If the API fails there as well, the issue is confirmed to be on the API side rather than Pabbly Connect.
  3. Endpoint Verification
    • Double-check headers, authentication method, and request body format used in your MCP tools.

If you continue to face issues, we can assist you over a live call to review the setup end-to-end.

Please book a slot using the link below:
https://calendly.com/d/ctw5-2bb-rct

Looking forward to your response.


I have reason to believe the transport method is also an issue. I change the method to https but it doesn't save. With each refresh it still appears as SSE. Please advise.
Preeti Paryani — Reply ·

Hey @unbleachedmuslin,

We have escalated this to our team for further review. Kindly allow us some time, and we will get back to you with an update as soon as we hear from them.

Thank you for your patience.

Preeti Paryani — Reply ·

Hi @unbleachedmuslin,

Thank you for your patience.

We’ve received an update from our team regarding this behavior. The transport method selection (SSE / Streamable HTTP) is currently not persisted, which means it will reset (default to SSE) upon page refresh.

This is expected behavior at the moment. The dropdown is primarily provided to help you copy the corresponding MCP Server URL based on the selected transport method, and it does not impact the underlying functionality.

If you select a transport method and copy the URL, it will work correctly for that specific option—even if the UI resets afterward.

Please let us know if you need any further clarification.

Back to all forum threads · Log in to reply