xyz2026

Hi @easymcpaisupport1

I have just had the following message back from SG’s support:

Hello Christian,

I have fixed the syntax of the file:

.well-known/oauth-authorization-server

and now jq successfully prints output when accessed:

Dimitar-Borukov:~ dimitar.borukov$ curl -s https://cyclinginandalusia.com/.well-known/oauth-authorization-server | jq { “issuer”: “https://cyclinginandalusia.com”, “authorization_endpoint”: “https://cyclinginandalusia.com/?easy_mcp_ai_oauth=authorize”, “token_endpoint”: “https://cyclinginandalusia.com/wp-json/easy-mcp-ai/v1/oauth/token”, “revocation_endpoint”: “https://cyclinginandalusia.com/wp-json/easy-mcp-ai/v1/oauth/revoke”, “response_types_supported”: [ “code” ], “response_modes_supported”: [ “query” ], “grant_types_supported”: [ “authorization_code”, “refresh_token” ], “code_challenge_methods_supported”: [ “S256” ], “token_endpoint_auth_methods_supported”: [ “none” ], “revocation_endpoint_auth_methods_supported”: [ “none” ], “scopes_supported”: [ “mcp”, “mcp:posts:read”, “mcp:posts:write”, “mcp:cpt:read”, “mcp:cpt:write”, “mcp:media:read”, “mcp:media:write”, “mcp:taxonomies:read”, “mcp:taxonomies:write”, “mcp:term_meta:read”, “mcp:term_meta:write”, “mcp:user_meta:read”, “mcp:user_meta:write”, “mcp:comments:read”, “mcp:comments:write”, “mcp:users:read”, “mcp:user_create:write”, “mcp:user_update:write”, “mcp:user_delete:write”, “mcp:menus:read”, “mcp:menus:write”, “mcp:blocks:read”, “mcp:blocks:write”, “mcp:appearance:write”, “mcp:plugins:read”, “mcp:settings:read”, “mcp:settings:write”, “mcp:woocommerce:read”, “mcp:woocommerce:write”, “mcp:wc_webhooks:write”, “mcp:acf:read”, “mcp:acf:write”, “mcp:buddypress:read”, “mcp:buddypress:write”, “mcp:events:read”, “mcp:events:write”, “mcp:yoast:read”, “mcp:yoast:write”, “mcp:aioseo:read”, “mcp:aioseo:write”, “mcp:rankmath:read”, “mcp:rankmath:write”, “mcp:seopress:read”, “mcp:seopress:write”, “mcp:slimseo:read”, “mcp:slimseo:write”, “mcp:tsf:read”, “mcp:tsf:write”, “mcp:gsc:read”, “mcp:ga:read”, “mcp:dfs:read”, “mcp:history:read”, “mcp:semrush:read”, “mcp:ahrefs:read”, “mcp:seranking:read”, “mcp:posts”, “mcp:cpt”, “mcp:media”, “mcp:taxonomies”, “mcp:term_meta”, “mcp:user_meta”, “mcp:comments”, “mcp:users”, “mcp:user_create”, “mcp:user_update”, “mcp:user_delete”, “mcp:menus”, “mcp:blocks”, “mcp:appearance”, “mcp:plugins”, “mcp:settings”, “mcp:woocommerce”, “mcp:wc_webhooks”, “mcp:acf”, “mcp:buddypress”, “mcp:events”, “mcp:yoast”, “mcp:aioseo”, “mcp:rankmath”, “mcp:seopress”, “mcp:slimseo”, “mcp:tsf”, “mcp:gsc”, “mcp:ga”, “mcp:dfs”, “mcp:history”, “mcp:semrush”, “mcp:ahrefs”, “mcp:seranking”, “mcp:abilities” ], “authorization_response_iss_parameter_supported”: true, “registration_endpoint”: “https://cyclinginandalusia.com/wp-json/easy-mcp-ai/v1/oauth/register”, “registration_endpoint_auth_methods_supported”: [ “none” ] }

Please check again with your developers if everything is working as expected.

If we could assist you with anything else, please do not hesitate to open a new request to our team and contact us again.

Best Regards,
Dimitar Borukov
Senior Technical Support Team

So please can you check again once more, with any luck it should now be ready, I think. If so, I’ll try connecting Claude.

Thanks,

Christian.

Hi @easymcpaisupport1,

Thanks again for coming back to me with more info.

I have just passed on this message to SG.

As soon as I have a reply and know more i’ll update you.

Thanks again for all your help.

I’m looking forward to finally getting this plugin to work!

Fingers crossed it will be possible!

Regards,

Christian.

Hi @easymcpaisupport1

Thanks for getting back to me, much appreciated.

Okay, i’ve just sent a copy of this message to SiteGround’s support, it’s on the same thread that has stayed open since the start, so hopefully, they’ll come back with a solution.

Thanks again for your help too.

Let’s see what happens.

Regards,

Christian.

Hi guys,

I spoke with SiteGround’s support, for them to check this in more detail, they are asking for:

– the exact URL that was called and responded with a 202
– the exact date, time, and timezone of the call that received a 202 response
– the IP address of the client that received the 202 response

Please can you provide these details so I can pass them on.

Furthermore, SiteGround have now said:

Based on the information provided, it seems that the issue is centered around the OAuth discovery, as the plugin is attempting to locate the file in the .well-known folder, which is governed by specific settings in the main Nginx configuration that cannot be altered. To address this, it may be beneficial to consult with the plugin provider to see if they can offer an alternative location for the OAuth file.

Does this make sense to you?

Many thanks,

Christian.

• This reply was modified 1 month, 3 weeks ago by xyz2026.