Property-graph database with Cypher, Graph Data Science, and Aura or self-managed deployment
Neo4j documents a property-graph database and its tooling at neo4j.com/docs/getting-started. The getting-started guide describes Cypher as Neo4j’s graph query language and links to data-modeling, import, application-integration, and visualization docs. It also points to Neo4j Graph Data Science, a library of graph algorithms, and GraphAcademy courses that include an Embedding & Vector Indexes tutorial. Neo4j MCP documentation lists running database options as Aura, Neo4j Desktop, or self-managed instances, and states that the official MCP server requires the APOC plugin on the instance it connects to. Use Neo4j when relationships among entities are the primary query pattern, and pair it with the neo4j-mcp catalog entry when agents need schema and Cypher access.
Use cases
- Model connected entities such as customers, documents, and dependencies as a graph
- Run Cypher pattern queries instead of multi-hop joins in a relational schema
- Apply Graph Data Science algorithms for centrality and path analysis
- Prototype graph-backed applications with official language drivers
- Connect agents through the separate neo4j-mcp entry once APOC is installed
Key features
- Property-graph data model documented in Neo4j getting-started materials
- Cypher graph query language for pattern matching over nodes and relationships
- Graph Data Science library of graph algorithms for analysts
- Import, modeling, visualization, and language-driver documentation
- Aura, Neo4j Desktop, and self-managed deployment options cited in Neo4j MCP docs
Who Is It For?
- Developers building applications where relationships are first-class data
- Analysts using Graph Data Science on an existing Neo4j graph
- Platform teams choosing Aura versus self-managed Neo4j for agent backends
Frequently Asked Questions
- Is Neo4j only a vector database?
- Neo4j getting-started docs describe a property-graph database. GraphAcademy lists an Embedding & Vector Indexes tutorial alongside the graph model; vector search is not the whole product.
- What query language does Neo4j document?
- Neo4j documents Cypher as its graph query language for expressing graph patterns.
- Does the database package include MCP?
- MCP is a separate official server documented at neo4j.com/docs/mcp. It connects to a running Aura, Desktop, or self-managed instance and requires APOC.
Related
Related
3 Indexed items
Voyage AI
Voyage AI documents state-of-the-art embedding models and rerankers at docs.voyageai.com for retrieval-augmented generation and semantic search. The embeddings API at POST https://api.voyageai.com/v1/embeddings converts text into dense vectors; the Python `voyageai` package exposes `voyageai.Client.embed()` with models such as voyage-4-large, voyage-4, voyage-4-lite, voyage-code-3, and domain-specific variants per docs.voyageai.com/docs/embeddings. Docs describe `input_type` query vs document prompts for retrieval tasks, optional `output_dimension` (256–2048), and `output_dtype` quantization (float, int8, binary). Rerankers score query–document relevance to refine initial retrieval results. Voyage AI is part of MongoDB's AI stack (MongoDB docs reference Voyage embeddings) and integrates with vector stores and LLMs as modular RAG components.
AssemblyAI
AssemblyAI documents Voice AI APIs at assemblyai.com/docs where developers transcribe and analyze audio via REST at `https://api.assemblyai.com` and real-time WebSockets at `wss://streaming.assemblyai.com` (EU pre-recorded host `api.eu.assemblyai.com` per cloud residency docs). Pre-recorded transcription requires an explicit `speech_models` array on every `POST /v2/transcript` request—docs recommend `universal-3-pro` with `universal-2` fallback for 99-language coverage. The platform also publishes a Voice Agent API for speech-to-speech agents, Speech Understanding features (diarization, sentiment, summarization), Guardrails, and an LLM Gateway to run frontier models on transcripts.
Chroma
Chroma documents an open-source embedding database at docs.trychroma.com for storing and querying vectors, metadata, and full-text fields in Python and JavaScript clients. Official guides cover ephemeral in-memory collections, persistent local storage, self-hosted server deployments, and Chroma Cloud at trychroma.com with authentication tokens. The docs describe collection CRUD, `add`/`query`/`get`/`update`/`delete` APIs, embedding functions (default and third-party), hybrid search, and multitenancy patterns for RAG and agent memory workloads per the documentation index.