đź’ˇ Feedback
Open

Public client ID for Craft Agents to use your MCP

Trying to access my capacities through Craft Agent's IDE. Looks like using Claude within Craft Agents is suggesting this:

Common causes for Capacities OAuth failures:

Redirect URI mismatch — Capacities supports Dynamic Client Registration, but if it's restricting redirect URIs, our app's callback may not be whitelisted. Pre-registered clients only — Capacities ships specific public client IDs for tools like LM Studio (lmstudio_mcp_capacities_public) and Cursor (cursor_mcp_capacities_public). It's possible their server only accepts those rather than DCR-registered clients. Space selection / consent screen issue — sometimes the consent step fails silently if no space is selected.

1 Comment

Sign in to comment

TC
Team Capacities
Team Capacities·6 months ago

Thanks for the detailed context, Greg. At the moment we only document specific public client IDs for certain tools (like LM Studio and Cursor), and there is no documented public client ID for Craft Agents. For a custom MCP client, the supported path is to follow the OAuth + Dynamic Client Registration flow described here: https://docs.capacities.io/developer/model-context-protocol. If Craft’s current implementation can’t complete that flow, please add details here so others can upvote and the team can consider first-class support.