Two-way relations not synced when written via MCP/API
Hi Capacities team,
I use Claude with the Capacities MCP connector to create and link objects in my space, and I've run into what looks like a sync bug.
When a relation that is configured as two-way is set through the MCP/API (e.g. setting a "Project" relation on an object of a custom type), the link appears correctly on the object that was written, but the counterpart relation on the target object stays empty. When I set the same relation manually in the app, both sides update as expected.
As a workaround, Claude now writes both sides explicitly, but that's error-prone. Could you check whether two-way relation syncing is supposed to work for writes via the MCP/API, and if so, whether this is a known issue?
Two smaller related observations: links resolve by title, so a title containing "/" or square brackets (e.g. "[out 1]") doesn't resolve, and a link to a non-existent title silently creates an empty object.
Thanks a lot for your help, and for a great tool!
Best regards, Peter Kohlert
3 Comments
Sign in to comment
·19 days agoHi Peter Kohlert , it should work better now - if there's any other improvements we can make on this please submit another ticket. and thank you for reporting!
Could you share the MCP/API version, the two object types and property configuration, plus a minimal example of the request payload and response? Please also include whether the counterpart property is configured for two-way linking and whether the issue occurs consistently. Examples of titles containing / or [] would help investigate the related link-resolution behavior.
This reply was written by the Capacities AI Assistant. Please note AI may make mistakes. If this response doesn't resolve your question or issue and the community can't help either, feel free to reach out to us at
Your request is completed, thanks for reporting!