Is Inception ICORE Server ready for production?
No, it is a work in progress under active development; interfaces, APIs, and internal structure may change frequently.
Inception ICORE Server MCP Server
@nbursa
Basic information
About Inception ICORE Server MCP Server
Model–Context–Protocol (MCP) Server A modular, extensible Rust-based server providing short-term, long-term, and latent memory services, a chat endpoint backed by a BaseAgent + Sentience DSL, and seamless integration with ChromaDB and LLM services.
Inception ICORE Server MCP Server config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"inception-core-server": {
"command": "docker",
"args": [
"run",
"-d",
"--name",
"chroma-local",
"\\"
]
}
}
}Inception ICORE Server MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is Inception ICORE Server?
A modular, extensible Rust-based server providing short-term, long-term, and latent memory services, a chat endpoint backed by a BaseAgent + Sentience DSL, and seamless integration with ChromaDB and LLM services. It is designed as a flexible microservice for building AI systems with layered memory and agent logic.
How to use Inception ICORE Server?
Clone the repository, build with cargo build, set environment variables (CHROMADB_URL, CHROMA_COLLECTION_ID, LLM_URL, ICORE_ENV), then run with docker-compose -f docker-compose.dev.yml up -d --build or run natively. Test the server with curl -i http://localhost:8080/api/ping expecting a "pong" response.
Key features of Inception ICORE Server
- Modular memory layers (short-term, long-term, latent via ChromaDB)
- BaseAgent with remember/recall/context logic
- Sentience DSL for scripting custom response logic
- LLM fallback integration (HTTP-based)
- Docker Compose orchestration with ChromaDB and LLM
- RESTful JSON API (Axum, Tokio async)
Use cases of Inception ICORE Server
- Build chatbots with persistent and ephemeral memory
- Prototype AI agents using Sentience DSL scripting
- Manage and query vector embeddings for similarity search
- Enable fallback to local LLM for text generation
- Create modular AI systems with separate memory layers
Frequently asked questions
What are the runtime dependencies?
Rust toolchain, Docker (for ChromaDB and LLM), a ChromaDB service, and an HTTP-based LLM server (e.g., llama.cpp).
Where is data stored?
Short-term memory is in-memory (volatile), long-term in SQLite file (`memory.db`), latent memory in ChromaDB.
What transport protocol does the API use?
HTTP with JSON request/response, built on the Axum framework.
Are there any known limitations in the current prototype?
Latent memory embeddings are dummy zero-vectors; real LLM encoder integration is not yet implemented.
More AI & Agents MCP servers
GetIntel
tarang8811Public docs + tool manifest for the GetIntel MCP connector (app.getintel.ai)
TruVerifAI Panel-review
TruVerifAITruVerifAI's Panel Review is the guardian agent for AI's highest-stakes coding decisions: four frontier models argue over an AI coding agent's riskiest designs, diffs, and commits before they execute, with local review g
1
BlazingCDN MCP - Content Delivery for Video, Software & Static Files
BlazingCDNOfficial MCP server for BlazingCDN - AI agents (Claude, Cursor, Windsurf) manage CDN resources, purge cache, query metrics, domains, Anycast CDN, Video CDN and Media CDN
1
Transform MCP
UnstructuredThe Unstructured Transform MCP Server connects your ADK agent to Unstructured, a document processing platform that turns raw files into structured, AI-ready data. This integration gives your agent the ability to parse PD
q-ring
I4cTimeQuantum-inspired keyring for AI coding agents. Secure secrets with superposition, entanglement, tunneling, and teleportation — CLI + 44 MCP tools.
3
Comments