Connect Guilduo MCP with OAuth and Agent linking

Check prerequisites

• Check that your client supports Remote HTTP MCP and OAuth. Setting names and availability depend on the client version.
• Sign in to your working account in the Web App and verify that you can read Quests.
• Register an Agent in Party for delegated work and check its Agent ID, which differs from its display name.

Connect to the canonical OAuth endpoint

1. In MCP, Apps or Connectors settings, name the connection Guilduo and choose Remote HTTP MCP.
2. Enter the endpoint above. Do not use /mcp-next or the Appwrite API URL for a normal connection.
3. Choose OAuth if an authentication option is offered. Do not paste an API key, Bearer token or client secret.
4. Sign in to the authorization flow with the same account as the Web App, review the permissions and grant access.
5. Return to the client and verify that the connection is marked connected or available.

https://mcp.guilduo.com/mcp

Link the connection to an Agent

linked: false with agent: null means the Agent is unlinked even after OAuth authentication. Check the Connections link before restarting OAuth.

1. Find the client you just connected in the Web App's Connections screen.
2. Link it to the intended registered Agent. Do not infer Agent identity from the client's name.
3. Reload the client and use get_current_agent_context to check linked, the Agent ID and effectiveExecutionScopes.

Verify without writing

An empty list can be valid if it matches that account's saved state. Discovering tool names alone does not verify call permissions or successful writes.

Verify my Guilduo connection using reads only.
Use get_current_agent_context and report the link state, Agent ID, role and effectiveExecutionScopes.
Read list_quests with view=all and limit=5; report only the result count.
Do not display tokens, Client IDs, UIDs or Quest content.
Do not change data or start additional model runs.

Diagnose connection failures

If an old migration-era connection is the cause, remove it and register the canonical endpoint again. For a working connection with stale tools, try Refresh first and avoid duplicates.