Anytype MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANYTYPE_API_KEY | Yes | Your Anytype API key obtained through authentication process |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| anytype_list_spacesB | Lista todos los espacios disponibles |
| anytype_get_spaceB | Obtiene un espacio específico por su ID |
| anytype_create_spaceC | Crea un nuevo espacio |
| anytype_update_spaceC | Actualiza un espacio existente |
| anytype_list_membersC | Lista todos los miembros de un espacio |
| anytype_get_memberC | Obtiene un miembro específico |
| anytype_search_objectsB | Busca objetos en todos los espacios o en un espacio específico |
| anytype_list_objectsC | Lista objetos en un espacio específico |
| anytype_get_objectC | Obtiene un objeto específico por su ID |
| anytype_create_objectC | Crea un nuevo objeto en un espacio |
| anytype_update_objectA | Actualiza un objeto existente. IMPORTANTE: Para actualizaciones de contenido (body/markdown), utiliza una estrategia de reemplazo que crea un nuevo objeto con el contenido actualizado y elimina el original, ya que la API de Anytype no actualiza correctamente el contenido markdown con el método tradicional. |
| anytype_delete_objectC | Elimina (archiva) un objeto |
| anytype_list_propertiesC | Lista todas las propiedades de un espacio |
| anytype_get_propertyC | Obtiene una propiedad específica |
| anytype_create_propertyC | Crea una nueva propiedad |
| anytype_update_propertyD | Actualiza una propiedad existente |
| anytype_delete_propertyC | Elimina una propiedad |
| anytype_list_typesC | Lista todos los tipos de objetos |
| anytype_get_typeC | Obtiene un tipo específico |
| anytype_create_typeC | Crea un nuevo tipo de objeto |
| anytype_update_typeC | Actualiza un tipo existente |
| anytype_delete_typeC | Elimina un tipo de objeto |
| anytype_list_tagsB | Lists all tags for a property |
| anytype_get_tagC | Gets a specific tag |
| anytype_create_tagC | Creates a new tag |
| anytype_update_tagC | Updates an existing tag |
| anytype_delete_tagC | Deletes a tag |
| anytype_list_templatesC | Lists all available templates for a specific type |
| anytype_get_templateC | Gets a specific template |
| anytype_add_to_collectionC | Adds an object to a collection |
| anytype_remove_from_collectionC | Removes an object from a collection |
| anytype_get_list_viewsB | Obtiene las vistas disponibles para una lista |
| anytype_get_list_objectsC | Obtiene objetos de una lista usando una vista específica |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Every tool has a clearly distinct purpose targeting specific resources (objects, spaces, properties, tags, types, collections, members, templates) and actions (create, get, list, update, delete, add/remove, search). No ambiguity exists between tools like anytype_get_object vs anytype_list_objects or anytype_create_property vs anytype_update_property. The descriptions reinforce distinct operations.
All 33 tools follow a perfect verb_noun pattern with the prefix 'anytype_' and snake_case throughout. The pattern is consistent: anytype_[action]_[resource] (e.g., anytype_create_object, anytype_get_space, anytype_list_tags). No deviations in style or convention exist across the toolset.
With 33 tools, the count is slightly high but reasonable for a comprehensive content management system covering spaces, objects, properties, types, tags, templates, members, and collections. Each tool appears to serve a specific purpose in the domain, though some consolidation might be possible (e.g., add/remove from collection could be one tool).
The toolset provides complete CRUD/lifecycle coverage for all core domain entities: spaces, objects, properties, types, tags, templates, and members. It includes create, get, list, update, and delete operations for each, plus search, collection management, and view handling. No obvious gaps exist; agents can perform full workflows without dead ends.