Have you read a contributing guide?
Current Behavior
I have asked Claude to create a task object and add three tasks. It has tried many times and insists this is a bug:
The instructions specifically mention creating tasks:
"Add a new object of type 'Task' with title 'Research AI trends'
Claude responded: Good catch — let me try following the instructions exactly as documented and create a Task using the built-in type name directly.
Thought process
Thought process
The user is pointing out that the Anytype MCP documentation/instructions specifically mention creating tasks using the built-in "Task" type. They're showing me an example instruction: "Add a new object of type 'Task' with title 'Research AI trends'"
This suggests that the Anytype MCP should support creating objects of the built-in Task type. Let me think about what I might be doing wrong.
Looking back at all my attempts:
When I used type_key: "task" with my custom task type present → it used my custom type
After deleting custom type, using type_key: "task" → returned type: null
When I tried updating objects with type_key: "task" → got an error saying the type key was invalid
But the documentation says this should work. I'm wondering if the system Task type uses a different key than "task", or maybe I need to reference it by its object ID instead. Looking at the system Task type from the list-types response, it has an ID and a key of "task", so that should be correct. Let me check what the actual type object structure shows.
There's a mismatch though - the layout shows "basic" instead of "action" like the list-types response indicated. That's confusing. I think I should just try creating a Task object with type_key "task" again now that I've cleaned things up. Maybe there was a caching issue, or the system needs time to propagate after I deleted my custom task type. Let me attempt it and see what happens.
Show less
Done
Good catch — let me try following the instructions exactly as documented and create a Task using the built-in type name directly.
API-create-object
API-create-object
Same result — type: null. This is a bug in the current Anytype MCP, not something I can work around. The task key is accepted without error but the built-in system type doesn't get assigned.
I'd recommend reporting it to the Anytype team with that exact example from their documentation — it's a clear, reproducible bug.
Expected Behavior
The task object is created with Type: task
Steps To Reproduce
- Add the MCP config to Claude
- Close and reopen claude
- start a new chat and ask it:
"Add a new object of type 'Task' with title 'Research AI trends' in the space 'My Space'
Environment
- OS: Mac OS Tahoe
- Version: 26.4.1
Anything else?
No response
Have you read a contributing guide?
Current Behavior
I have asked Claude to create a task object and add three tasks. It has tried many times and insists this is a bug:
The instructions specifically mention creating tasks:
"Add a new object of type 'Task' with title 'Research AI trends'
Claude responded: Good catch — let me try following the instructions exactly as documented and create a Task using the built-in type name directly.
Thought process
Thought process
The user is pointing out that the Anytype MCP documentation/instructions specifically mention creating tasks using the built-in "Task" type. They're showing me an example instruction: "Add a new object of type 'Task' with title 'Research AI trends'"
This suggests that the Anytype MCP should support creating objects of the built-in Task type. Let me think about what I might be doing wrong.
Looking back at all my attempts:
When I used type_key: "task" with my custom task type present → it used my custom type
After deleting custom type, using type_key: "task" → returned type: null
When I tried updating objects with type_key: "task" → got an error saying the type key was invalid
But the documentation says this should work. I'm wondering if the system Task type uses a different key than "task", or maybe I need to reference it by its object ID instead. Looking at the system Task type from the list-types response, it has an ID and a key of "task", so that should be correct. Let me check what the actual type object structure shows.
There's a mismatch though - the layout shows "basic" instead of "action" like the list-types response indicated. That's confusing. I think I should just try creating a Task object with type_key "task" again now that I've cleaned things up. Maybe there was a caching issue, or the system needs time to propagate after I deleted my custom task type. Let me attempt it and see what happens.
Show less
Done
Good catch — let me try following the instructions exactly as documented and create a Task using the built-in type name directly.
API-create-object
API-create-object
Same result — type: null. This is a bug in the current Anytype MCP, not something I can work around. The task key is accepted without error but the built-in system type doesn't get assigned.
I'd recommend reporting it to the Anytype team with that exact example from their documentation — it's a clear, reproducible bug.
Expected Behavior
The task object is created with Type: task
Steps To Reproduce
"Add a new object of type 'Task' with title 'Research AI trends' in the space 'My Space'
Environment
Anything else?
No response