enhancement: Adding (optional ?) API/MCP support to make AnyType API available 24/7 for automations

[ebanDev]

Problem

Currently, the MCP/API is only available from the anytype client on desktop, which is quite annoying because it doesn't allow for automations in the background to interact with AnyType (creating tasks, changing data, anything)

Proposal

Make, in some way, the MCP/API server available from outside to allow building automations.

Additional context

Here are a few useful links I came across :

• AnyType's MCP : https://github.com/anyproto/anytype-mcp
• AnyType's API Docs : https://developers.anytype.io/docs/
• AnyType's ProtoBuf API seems to be located inside of the anytype-heart repo, so I guess you'd basically need to spin up a anytype-heart instance linked to the sync bundle ?

[ebanDev]

Hello again! So I took some time and created ✨ anytype-jsonapi-docker ✨, a simple headless docker container that runs anytype-heart, enables the JSON API and exposes it. For now it uses AnyType's official production sync servers, but maybe you could use this as a base to integrate it with your sync bundle.
Best,
Eban

[grishy]

Great!
Can you send a few examples of how to use it? I think it will work smoothly with the bundle because we have all the same services on one port.

[ebanDev]

To make it work simply set the .env variable as explained in the README, then you'll be able to query the JSON API as per the docs https://developers.anytype.io/docs/guides/get-started/spaces :) However I do not know how to change the sync server to a custom one, you may want to ask an LLM!

[grishy]

NOTE:
Here is some original code - https://github.com/anyproto/anytype-cli
And docs - https://developers.anytype.io/

[benwilks]

Would also love to have the new antype-cli https://github.com/anyproto/anytype-cli integrated into the any-sync-bundle to enable a headless anytype instance for api / automation to run from a server!

[leodrivera]

I'd love to have this feature too