Deploy graphiti-mcp-but-working-railway
Railway-friendly template/fork of michabbb/graphiti-mcp-but-working
graphiti-mcp-but-working-railway
Just deployed
Deploy and Host graphiti-mcp-but-working-railway on Railway
This template builds a fork of the michabbb/graphiti-mcp-but-working repo, but with Railway-friendly Dockerfile and variables. No external networking by default.
About Hosting graphiti-mcp-but-working-railway
This requires a running Neo4j database, Redis, and API keys for LLM's of choice.
Deployment Dependencies
Dependencies for graphiti-mcp-but-working-railway Hosting
- Neo4j
- Redis
Common Use Cases
Used for AI-managed Knowledge Graph management.
Why Deploy graphiti-mcp-but-working-railway on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying graphiti-mcp-but-working-railway on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
graphiti-mcp-but-working-railway
trichard3000/graphiti-mcp-but-working-railwayNEO4J_PASSWORD
Password for Neo4j database
OPENAI_API_KEY
Key for OpenAI API
REDIS_PASSWORD
Password for Redis instance
CLEAR_GRAPH_PASSWORD
Password to use when clearing the Graph db
